You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
If we try to use the resource time ranges feature and we specify the start date (time), for some item, to be less than the current start date (time) of the scheduler then the label for that item will not be visible initially. We have managed to find a workaround for this by setting the start date of the item to be the same as the start date (time) of the calendar.
Is there some other solution for this or this is a bug?
Example:
If we set the startDate for an item: new Date(2019, 0, 1, 6), where the 6 is starting hour everything is working fine because that is the same startDate for the scheduler. If we set the start date to be new Date(2019, 0, 1) then the "TEST" label is not visible initially. It becomes visible if a user changes the window size.
Reproduced (the label appears on scrolling). The steps are on the following screencast:
Forum post
Hello,
If we try to use the resource time ranges feature and we specify the start date (time), for some item, to be less than the current start date (time) of the scheduler then the label for that item will not be visible initially. We have managed to find a workaround for this by setting the start date of the item to be the same as the start date (time) of the calendar.
Is there some other solution for this or this is a bug?
Example:
If we set the startDate for an item: new Date(2019, 0, 1, 6), where the 6 is starting hour everything is working fine because that is the same startDate for the scheduler. If we set the start date to be new Date(2019, 0, 1) then the "TEST" label is not visible initially. It becomes visible if a user changes the window size.
We have manged to reproduce this behaveiour here
https://www.bryntum.com/examples/scheduler/resourcetimeranges/
with the following code:
The text was updated successfully, but these errors were encountered: