Our pure JavaScript Scheduler component


Post by po-igp »

Hey there,

when zooming out of the scheduler, we sometimes receive this error and events start bugging:
Image

We are not quite sure if this error is caused by our own code, so is there any workaround or fix for this issue?
This error seems to occur both on Bryntum version 4.2.1 as well as 5.0.0

Best regards

Attachments
bryntum.gif
bryntum.gif (7.98 MiB) Viewed 468 times

Post by tasnim »

Are you able to reproduce it in our online example https://bryntum.com/examples/scheduler-pro/resourcehistogram/ ?


Post by po-igp »

Hello tasnim,

we are not able to reproduce the error with your online example.

Best regards


Post by alex.l »

Please attach an app where it will be possible to reproduce that and we will be able to investigate this problem.

All the best,
Alex


Post by po-igp »

Hey there,

because the app is to big for attachments, here's WeTransfer link to download:
https://we.tl/t-BIV243jYHS

To run the app run this in your command prompt:

npm i
npm i - g quasar
npm install -g @quasar/cli
quasar dev

with this you should be able to run the app.

Best regards


Post by alex.l »

Please review attached video. What should I do to reproduce the error.
I was need to add this line into package.json to make the app runnable

"vue-template-compiler": "~2.6.10"

Maybe this info is important.

Attachments
Screen Recording 2022-09-15 at 15.59.32.mov
(14.24 MiB) Downloaded 28 times

All the best,
Alex


Post by po-igp »

Hello Alex,

adding vue-template-compiler seems to do not solve the problem.

To reproduce the error, you need to zoom out (either by CTRL + mouse wheel or clicking the button in the top right corner).

Best Regards


Post by alex.l »

adding vue-template-compiler seems to do not solve the problem.

I was talking about your test case, I had to apply this fix to make it runnable and check.

Could you please try to upgrade your app to version 5.1, it fixed problem to me.
Please let us know if it worked for you.

All the best,
Alex


Post by po-igp »

Hello Alex,

it looks like upgrading the app to version 5.1 fixed it.
Thank you for your help.

Best regards


Post Reply