Support Forum

We are experiencing the same with Firefox 92.
We are using suspendRefresh() and resumeRefresh() in our code, as in the above mentioned demo (big dataset).

Thanks,

Giovanni

Dear Bryntum team, As far as we've understood you manage to have quite good performances in Scheduler 4.1 but we don't see anything new in the nightly/beta changelogs. Performances are really an important matter in our application and we won't upgrade the Scheduler until we'll have the 3.x performan...

Thanks Johan, Unfortunately I still can see this on the latest beta release ( bryntum-scheduler-4.1.0-beta-2 ). I attach a video to reproduce the onElementResize . Apparently the onElementResize is going to re-render everything because the scheduler width changed. Indeed when you start with 5 resour...

@mats: The test case for the "onElementResize" is visible on the bigdataset demo. Bryntum Scheduler version: 4.1.0-beta-1 - 2021-01-15 Steps to reproduce: Replace this line: scheduler.suspendRefresh(); with: scheduler.eventStore.beginBatch(); scheduler.resourceStore.beginBatch(); Replace t...

Regarding the "onElementResize" function which takes about 700ms for you. I cannot reproduce it. You can see on the screenshot that it takes 0.17ms in Big dataset demo. Please submit a runnable testcase that we can inspect. Cheers! Снимок экрана 2021-02-09 в 20.37.51.png Regarding this on...

Thanks Pavel for taking care of this. Performances in our application are really important so we reverted to Scheduler 3.x. As soon as you have an ETA about the fix, can you please let us know? About the "onElementResize", I'll have a deeper look and I'll see if I can reproduce it on a dem...

Actually there's a simple way to reproduce this exploiting the bigdataset example: Let's consider a dataset of 5K events (200 resources * 25 events). I obtain the following results: Bryntum Scheduler 3.0.4 generate: 32.22 ms data: 460.38 ms Bryntum Scheduler 4.1.0-beta-1 generate: 123.47 ms data: 83...

Dear Bryntum team, We noticed some performance degradation upgrading the Scheduler component from 3.0.4 to 4.0.7. We observed that with 150 events (10 resources, each with 15 events) the time required to render all the events on the UI is doubled (from 1 sec to 2 secs). We've noticed there's a simil...

In order to reproduce the bug you can start from this demo https://www.bryntum.com/examples/scheduler/eventmenu/ adding the following listener listeners : { beforeeventdropfinalize(event) { console.log(event.context); console.log(event.context.valid); event.context.async = true; setTimeout(() => { e...