Closed marciogurka closed 6 months ago
Project has a config limiting calendars iteration timspan: https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-maxCalendarRange You need to adjust it accordingly in case you deal with large timespans.
Forum post
"Hey Team,
We just figured that the duration calculation of calendars is incorrect for large timespans. We used this example https://bryntum.com/products/schedulerpro/examples/event-non-working-time/ with the attached code. If you open the dev console you will see that the duration for the two timeranges (01.01.2024 - 30.12.2035, 01.01.2024 - 30.12.2045) is the same (112579200000 ms).
The function is crucial to our business logic so this is a major flaw for us currently.
Thanks in advance."
Go to https://bryntum.com/products/schedulerpro/examples/event-non-working-time/ and use the following code
the duration in ms in both console logs are the same, even with 10 years difference.