Search found 2325 matches

Indeed, it seems destroying the gantt does not free the allocated memory (at least in that example), we'll be fixing this. Ticket created: https://github.com/bryntum/support/issues/8853

We have this mechanism (marking user input as such, to distinguish it from dependent changes) in the development already. It should appear in the 6.0.0 release (tentatively scheduled for April). It will be experimental and private (undocumented) API initially, but we can tweak it, based on your feed...

Ok, I see. We'll discuss internally what can be done here.

In the meantime, please try analyzing the first InsertChildAction in the transaction.

What about other cases when some change triggers changes in the dependent data? For example, when you change percent done of some task, the percent done of its parents will be changed, when you move some task - it successors will be moved as well, etc. For this scenarios, do you also plan to only se...
@ahmad.siddique Hi, I want to fetch the item that caused the transaction. I guess, in this particular case, you can check the 1st action that updates the parent of the event InsertChildAction - that might be the source of the outdent transaction. However, what is your overall goal for this? Thing is...

I'll check this scenario soon and get back to you.

I don't really observe the behavior you are describing. See the video here: https://streamable.com/02otz1

Perhaps you have some Chrome plugins?

@pfund This issue is caused by the way of how the ALAP status is propagated in the dataset. Currently, it is propagated down to all successors of the ALAP task. In your dataset, Task21 is set as ALAP and that propagates the ALAP status downstream to all successors, among which are the tasks 33 and 3...

@dominicdolan What version of our component do you use? IIRC we've fixed this issue recently, please try to reproduce with the latest code?