Our pure JavaScript Scheduler component


Post by odiyaerlichster »

Hi,
I noticed you added a new feature in 5.6.7
"If Scheduler Pro is not provided with the viewport start date on creation, it now tries to use the project's start date, or calculates the earliest start date among all events"
This is causing us a lot of issues, as we have an async start date calculation after the scheduler is created where the scheduler should start.
What's happening now is that the scheduler at first starts on the date we tell it to , and the "jumps" to some random date I guess is calculated from here.
How can I prevent this feature from happening/working?

Thanks!


Post by nickolay »

Hi,

You can provide a startDate : new Date() config for the scheduler during instantiation. This will disable the calculation of earliest date and match the old behavior for the case when no startDate config was provided.


Post Reply