There seems to be a bug with recurring resourceTimeRanges.
When initially loading the scheduler they are not visible until some update happens.
In this example I used the time range demo and simply made an event recurring. Then I set the start date beyond its initial date so only the recurrence is visible.
bryntum_time_range.gif (915.41 KiB) Viewed 1498 times
I'm using the recurring time ranges to indicate non-working days of resources but due to this bug and bad performance it's not looking like a good option. When doing a simple new setup of the scheduler and adding work regimens for 25 resources it already slows down the scheduler greatly.
Since the project I'm working on is quite urgent is there some other/better way to achieve my purpose?
And Thank you for your report
Please let us know if you have any other question.
Re: Recurring resourceTimeRanges render bug
Posted: Mon Dec 12, 2022 9:23 am
by gerts
This is already the 5th bug in a short time that I had to report. Up to today, none has been fixed.
Due to this, we struggle to meet our deadline for the project.
Can you let me know when fixes can be expected? Or at least try to help with workarounds?
Since the resource time range has this bug and causes bad performance I was wondering if there is a better way to indicate irregular non-working days?
Thanks a lot!
Re: Recurring resourceTimeRanges render bug
Posted: Mon Dec 12, 2022 9:47 am
by tasnim
Can you let me know when fixes can be expected?
This is not on the list of the nearest release so can't give an exact date
What we are trying to do should perfectly work in Scheduler, if there was no bug. So advice to upgrade to a more expensive version is not exactly what I was asking for...
Re: Recurring resourceTimeRanges render bug
Posted: Mon Dec 12, 2022 1:42 pm
by tasnim
Hell Gerts,
Unfortunately, can't make any promises about when this bug will be fixed, We'll try to fix it ASAP. Please subscribe to the ticket so that it will notify you when it fixes.