[REACT] Bryntum scheduler event update with dependency - Rerender

[lai.le@arent3d.com]

Hi Nickolay

4) For efficiency, when loading data, it is rendered as-is right away, and only then the scheduling logic is applied. So event 584 is first rendered at 2023-07-10 then dependencies logic moves it to 2023-07-07
5) To avoid this "visual jump" need to make sure the persisted data is saved already after the scheduling logic has been applied.

I don't quite understand this part, could you provide an example based on the code I've sent?

[nickolay]

Hello,

What exactly is not clear?

[lai.le@arent3d.com]

I don't understand what 'persisted data' means here; I haven't changed any data

[nickolay]

Persisted data is the data you are loading (assuming it comes from some persistent data storage, like database). In this case, the persisted data is different from the data with scheduling logic applied - thus the visual "jump" happens.