RadiantQ Forum
Product => WPF Gantt Package => Topic started by: tim on April 30, 2020, 12:11:06 PM
-
I've uploaded a video that shows our problem:
https://my.hidrive.com/lnk/PChJJXNb
When I drag a new task into the Gantt and there already is an existing one at its position most of the time they will be rendered upon each other. Only when I click the existing one the view becomes refreshed and they are separately drawn above each other, as we want it to be.
As far as I can see it is developed as it is recommended here:
http://www.radiantq.com/Docs/WPFGantt/UsersGuide/WPFGanttUsersGuide.html?OverlappedTasksLook
OverlappedTasksRenderingOptimization is set to "ShrinkHeight" is and there is a RowHeightBinding that will cause the row height to expand.
Any ideas on this?
I've found mentions of two properties that sound interesting for this problem. Could you please describe what they do and if they might be of help here?
1. In the release notes of version 8 (http://radiantq.com/new-year-release-wpf-gantt-package-8-0/): "Ability to refresh overlapped tasks layout with TasksListControl.RefreshOverlappedBars."
2. In the release notes of version 9 (http://newforum.radiantq.com/index.php?topic=109.0): ""BeforeOverlappingSet" event in FlexyGantt to handle events when overlapping of tasks occurs (to customize the default overlapping behavior). Illustrated in CollapsingTasks sample.."
Thanks!
Jan
-
Jan,
We are looking on this, will update you soon.
Thanks
Raja
-
Jan,
We tried reproducing the issue in installed sample unfortunately we couldn't. Can you please share the reference sample so that we could try on it.
RefreshOverlappedBars - refreshes overlapped tasks layout with TasksListControl.RefreshOverlappedBars
BeforeOverlappingSet - an event that triggers before two tasks overlap
Thanks,
Raja.
-
Hi,
unfortunately I cannot share our whole application, where it is reproducable and I cannot reproduce in the samples either.
What seems to help is to manually call RefreshOverlappedBars() on the TasksListControl in the ChartRow_Drop event handler. However this feels a bit like a workaround for something that should work w/o taking care of it manually but at least it seems to work. :)
Thanks
Jan