In Ext Gantt v.2.5.1 such dependencies automatically shortened
So when i dragging dependent tasks, component saves it, but recalculates on next page loading
Which behavior is right?
Support Forum
in Ext Gantt v.2.2.25 dependencies with '0' lag and linked tasks width different start dates drawed from start date (from task) to enddate (to task).
In Ext Gantt v.2.5.1 such dependencies automatically shortened
So when i dragging dependent tasks, component saves it, but recalculates on next page loading
Which behavior is right?
In Ext Gantt v.2.5.1 such dependencies automatically shortened
So when i dragging dependent tasks, component saves it, but recalculates on next page loading
Which behavior is right?
- Attachments
-
- before save
- 1.png (23.12 KiB) Viewed 3197 times
-
- after save
- 2.png (20.61 KiB) Viewed 3197 times
2.5 behavior is right, it has cascadeChanges enabled by default and a dependency should have Lag set to describe your initial UI, otherwise you're kind of breaking the dependency.
Please see: https://www.bryntum.com/products/gantt-for-extjs/docs/ ... g-lagField
Please see: https://www.bryntum.com/products/gantt-for-extjs/docs/ ... g-lagField
Good question. Thing is the code was modified quite seriously in 2.5.0 release to support the constraints mechanism.
That's why this behavior has changed. And turbulence related to this modification is still not resolved completely.
Thank you very much for the report. This behavior is by design for sure ..so not a bug. But we'll discuss internally options to support your use case. Here is a ticket to track: https://www.assembla.com/spaces/bryntum ... y-in-2-5-x
That's why this behavior has changed. And turbulence related to this modification is still not resolved completely.
Thank you very much for the report. This behavior is by design for sure ..so not a bug. But we'll discuss internally options to support your use case. Here is a ticket to track: https://www.assembla.com/spaces/bryntum ... y-in-2-5-x
We have implemented a "manually scheduled" flag for dependencies. Manually scheduled dependencies are ignored during dependency constraint calculation. They are rendered with a dashed line instead of a solid line, so the user can immediately see the difference.
We have also added an action to reschedule a task, where the task and its incoming dependencies are temporarily treated as automatically scheduled. This action is only available under certain conditions, namely when the task is manually scheduled or all incoming dependencies are manual.
We'd like to see this feature added to the standard, thereby removing the need for our overrides.
Regards,
Christian Semrau
We have also added an action to reschedule a task, where the task and its incoming dependencies are temporarily treated as automatically scheduled. This action is only available under certain conditions, namely when the task is manually scheduled or all incoming dependencies are manual.
We'd like to see this feature added to the standard, thereby removing the need for our overrides.
Regards,
Christian Semrau