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
Not showing rooms in breaks in the linear schedule is bad, because there may be concurrent break-like events that actually rely on the room information.
However, always showing the room(s) is also bad, because often you just have a general break, and you don't want all five room names attached to the coffee break, especially on the limited screen size that is usually the cause of the linear schedule being used.
We can't just check if the break is across all rooms, because not all rooms are used on all days, so we'd have to replicate the "which rooms are in use" logic from the grid schedule, to then check if the grouped break applies to all of them.
The text was updated successfully, but these errors were encountered:
Not showing rooms in breaks in the linear schedule is bad, because there may be concurrent break-like events that actually rely on the room information.
However, always showing the room(s) is also bad, because often you just have a general break, and you don't want all five room names attached to the coffee break, especially on the limited screen size that is usually the cause of the linear schedule being used.
We can't just check if the break is across all rooms, because not all rooms are used on all days, so we'd have to replicate the "which rooms are in use" logic from the grid schedule, to then check if the grouped break applies to all of them.
The text was updated successfully, but these errors were encountered: