Overlay vs Daemon
Overlay (one shot)
- Starts immediately and exits when you close it
- Simple and predictable
- Best for quick annotations
- Can open a named session with
--session-file
Command:
wayscriber --active
wayscriber --active --session-file ~/Documents/lecture-04.wayscriber-session
Daemon (background)
- Runs in the background and keeps your drawings between toggles
- Faster to access during presentations
- Works well with a keybind
- Can be targeted by named-session toggle requests
Command:
wayscriber --daemon
wayscriber --daemon-toggle
wayscriber --daemon-toggle --session-file ~/Documents/meeting.wayscriber-session
If installed, the systemd user service is the most reliable way to keep the daemon running. Use only one compositor/global toggle binding; duplicate bindings can fire twice and immediately undo the toggle.
Overlay UI
The side toolbar is where most runtime UI management lives. It has four top-level panes:
- Draw pane: colors, presets, thickness, and tool-specific controls.
- Canvas pane: pages, boards, actions, zoom, and step controls.
- Session pane: Open, Save As, Info, Clear, recent sessions, and Manager. See Sessions and Session Manager for named-session workflows.
- Settings pane: status/toolbar toggles, config file/configurator shortcuts, section toggles, and toolbar customization.
Side toolbar sections can be collapsed from their headers while working. Toolbar
customization changes are saved to config.toml, so the next overlay or daemon start
keeps the same visible items and order.
See Toolbars for the top strip, GTK4/builtin frontend selection, minimized restore tabs, shortcut badges, and width-aware overflow behavior.