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.
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.
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
If you edit a cell and directly change to another row in the TaskEdited event the TaskEditedEventArgs holds the old Task value before the editing.
If a task is partially visible in the Timeline area, it should be bring into view when is selected by default.
The Width of the ColumnDefinition is not updated after resizing it via the resizers.
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.
Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release.
When scaling RadGanttView control in order to print the visible area in one page width only, extra empty pages are generated.
If the following steps are performed: - Hold the Ctrl keyboard key - Highlight a task by clicking it with the mouse - Highlight a second task - Release the Ctrl key - Click the first task again Cause the second highlighted task to still be highlighted.
When removing Tasks that are not visible (the parent task is collapsed) an ArgumentOutOfRangeException is thrown.
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.
When collapsing the parent task first and then the child tasks a System.OverflowException is thrown.