This reproduces with recurring tasks.

Scheduled for:
The fix for this issue will be available with LIB (version 2019.1.128) scheduled for publishing on Monday, 28th January 2019.
 

This reproduces with recurring tasks.

Scheduled for:
The fix for this issue will be available with LIB (version 2019.1.128) scheduled for publishing on Monday, 28th January 2019.

If you have a GanttTask(s) added in the RadGanttView control, and the DPI is higher than 100%, the UI is almost unresponsive. Also, the newly added tasks are not visible until you resize the control.

When the Window OS DPI setting is set above 100% resizing the grid portion's columns with their resizer controls leads to unresponsive UI and possible application crash.

The issue is only reproduced if the InitialExpandBehavior is set to Collapsed.

Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release.

Available in LIB version 2015.3.1123, it will be also available in the 2016 Q1 release.

There are two scenarios where the issue can be seen:

 - at startup when the ColumnDefinition’s Width is set to AutoHeaderAndContent its Width is rendered incorrectly;

- when you change the PixelLenght;

The issue could be observed in the attached short video

When collapsing the parent task first and then the child tasks a System.OverflowException is thrown.

Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release. 

When removing Tasks that are not visible (the parent task is collapsed) an ArgumentOutOfRangeException is thrown.

If the current culture (German) is set to a culture with 24 format the default 12 format is used in the TimeRuler and the dragging/resizing Tooltip of the control.

Available in LIB version 2016.2.530, it will be also available in the 2016 R2 SP1.

If the TasksSource is cleared in the TaskEdited event of the control the event is called in a loop.

Available in LIB version 2016.2.530, it will be also available in the 2016 R2 SP1.

If the Timeline part of the control is shrunk to a state it doesn't need a scroll bar anymore (by changing PixelLength or VisibleRange) and after that it is enlarged, its size doesn't change, but the ScrollBar values update.

Available in LIB version 2016.2.627, it will be also available in the 2016 R3 release.