[REACT] - All events "flicker" when ever an event is dragged or created or resized

[odiyaerlichster]

Hi,
I see an issue occurring in your demos that is also occurring to us.
When ever a new event is created, dragged, or resized - all events on the screen appear to flicker.
This seems to only happen when rendering as JSX component for the event.
This reproduces on this demo: https://bryntum.com/products/schedulerpro/examples-scheduler/frameworks/react-vite/renderer-context/dist/

Attached is a also a screen recording where you can see this issue occurring:

Screen Recording 2024-02-04 at 16.03.01.mov

(3.02 MiB) Downloaded 39 times

I would appreciate if you could look into this issue as soon as possible.
Thanks,
Odiya Erlichster

[mats]

Yes, that's a really bad bug, we'll get it fixed asap! https://github.com/bryntum/support/issues/8464

[odiyaerlichster]

Hi!
Any updates on when this fix will be available?
Thanks!

[mats]

Issue is now resolved and will be released hopefully later this week!

[odiyaerlichster]

Amazing! Thanks!

[mightym]

@mats is that issue also related to jsx events flickering when the event data is updated from remote?
Whenever my event array (which I pass to the scheduler) gets updated, all my events are flickering.

[ghulam.ghous]

Hi Mightym,

I have checked by changing the events data from remote, and the events are not flickering anymore with the current fix.

Regards,
Ghous

[mightym]

Awesome Ghous! Looking forward to the new version. Thanks!

[mightym]

Yeah! Just installed 5.6.7 and the flickering is gone
Though I'm not getting a warning in my react components about :

console.js:213 Warning: flushSync was called from inside a lifecycle method. React cannot flush when React is already rendering. Consider moving this call to a scheduler task or micro task.
    at BryntumSchedulerPro (http://localhost:5173/@fs/Users/mark/Developer/bryntum-test-client/node_modules/.vite/deps/@bryntum_schedulerpro-react.js?v=b4b984b7:10755:5)

[ghulam.ghous]

Hi there,

We are glad that it all worked . About the warning, you can ignore it. It is a known thing and maybe in future we address it. But as it is not affecting any thing we have decided to let go for now.

Regards,
Ghous