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
At the moment we hardcode a changeover of one slot in the scheduler. Live music needs longer than this, so in the past we've hacked it by increasing the duration, which is not ideal.
Proposals should have a setup time field so we can override the setup time for these kind of proposals.
(Do we need a teardown time field as well?)
The text was updated successfully, but these errors were encountered:
An alternative/additional way of doing this would be to set a changeover time per timeslot type (e.g. talks in stage A get 10 minutes but performances in A get 20minutes...)
@SamLR That's pretty much how it currently works, the problem is that we need this customisable on a per-proposal basis as some things (generally weird ones) need longer setup times. An example of this was foxdog in 2024 who needed an abnormally long setup time. We bodged it by increasing their slot time so it was properly scheduled, but forgot to decrease it afterwards, which lead to everyone showing up early...
I am also desperately trying to remember why music was a problem and we were showing gigs running after the licensed time, which I had to fix more than once during the event. Anyone remember?
I am also desperately trying to remember why music was a problem and we were showing gigs running after the licensed time, which I had to fix more than once during the event. Anyone remember?
I don't think it really matters because timeslots should definitely fix this problem.
At the moment we hardcode a changeover of one slot in the scheduler. Live music needs longer than this, so in the past we've hacked it by increasing the duration, which is not ideal.
Proposals should have a setup time field so we can override the setup time for these kind of proposals.
(Do we need a teardown time field as well?)
The text was updated successfully, but these errors were encountered: