Hi all,
Based on that post and my previous comment the following github issue was created: https://github.com/bryntum/support/issues/5889.
The above issue is now marked as closed, however I'm still observing the issue with converting events to the given time zone iana.
Let me describe step by step the problem.
- In our product, we work with large data set. Our servers return with e.g.: 10k records (events).
- The start and end date returned from back-end is iso string e.g.: start date - 2023-05-02T13:00:00.000Z
- We would like to configure the bryntum scheduler to display that event in the given time zone iana (e.g.: if 'Europe/Sofia' (UTC+3) - the scheduler should display the event at 16:00 if event start date is '2023-05-02T13:00:00.000Z').
What, I can see in the bryntum 5.3.4 is:
Prerequisites:
My notebook is now in UTC+2
The bryntum scheduler gets 'Europe/Sofia' time zone configuration (UTC+3)
Server return 10k events. One of the event starts at 2023-05-02T13:00:00.000Z
What is happening then:
- The timeline's headers are in line with Europe/Sofia
- The current time line is inline with Europe/Sofia
- When the events are loaded from the server, and once they come into the EventStore the scheduler displays them as in UTC+2
- After a moment (seconds) the bryntum scheduler moves the events from UTC+2 to UTC+3.
In the attachment, I provided the demo.
Is there anything else you can improve regarding timezones and first rendering ?
I bet, you are challenging with some async code and not sure how hard is it for you to ensure all events are converted into the given timezone right away and that the user does not see that movement (from UTC+2 to UTC+3).
We are waiting for that feature for quite some time, we are starting wondering if our code need the way around or we can wait for you.
Best regards,
Kornel