Managing events
Found under admin area "Event management" > "My events". Every event is listed with name, period or date, note, counters and disk usage; the loaded event is highlighted.
Actions per event#
| Button | Effect |
|---|---|
| Load | Makes the event the active one. Layouts, graphics, access code and limits travel with it |
| Duplicate | Creates a copy without pictures. The quick settings PIN is copied along |
| Period/schedule | Set start and end, see below |
| Reset counters | Sets sessions, pictures, animations and prints to zero. The pictures themselves stay |
| Archive | Removes the event from the selection while keeping it complete. "Show archived events" brings it back into the list |
| Delete | Removes the event. You are asked whether the pictures should go too |
A note per event holds what would otherwise end up on a scrap of paper — contact person, teardown time, special arrangements. It is only visible internally.
Scheduling and automatic loading#
"Period/schedule" defines when the event applies:
- Start and end with times, across midnight as well. If the party ends after midnight, simply enter the following day's date as the end.
- Without an end, the period runs to the end of the starting day.
- Without a period nothing changes: the event is loaded by hand.
What follows from that:
- At startup the event is loaded automatically if its period is currently running — even after a restart in the middle of the party.
- While running, the admin area suggests loading the matching event when you sign in. The switch only happens after confirmation, because it exchanges layouts, graphics, access code and limits.
- If two periods overlap, the one that started most recently is suggested; both events are kept.
- The head of the list states which event will be loaded next by itself.
Date and time are set on a screen of their own: a month calendar with large day tiles, times in quarter-hour steps, plus "Today", "Tomorrow", "Next Saturday" and "In a week".
Event picker at startup#
The switch "Show event picker at startup" makes the booth ask which event to load when the program starts. The picker appears instead of the start screen and waits without a timeout; "Continue without switching" keeps the last loaded event. The question is asked once per program start.
With the option off, the last loaded event simply continues — the right setting for kiosk operation with autostart. If a scheduled event's period is running, the picker is skipped anyway and that event is loaded.
Backing up, moving, handing over#
Below the event list, "Import / export" leads to event packages. A package contains the settings, layouts, digital backgrounds and graphics of a party — and, if you want, its pictures.
On export you choose whether the pictures come along; the checkbox states in advance how much extra space they need. Archived events can be backed up as well.
The package also contains the access code and the quick settings PIN — so that a backup after a device failure is complete and QR codes already handed out still work.
On import a new event is always created; an existing one is never overwritten. The access code from the package is kept so that QR codes handed out keep working. If it is already in use on this booth, a new one is generated automatically.
After the import the event exists but is not loaded yet — tap "Load" in the list for that.