I think hiding/unhiding upon receiving SIGUSR2 can be useful in a couple of ways, for example:
- keyboard-focused setups
- window manager that lack indicators when switching between windows/desktops (by showing the tasklist)
- making a good looking dock-like bar without killing and re-running tint2 (by using the launcher item)
I'm proposing to bind this behavior to a signal for better customizability: I can use my window manager/hotkey daemon for keyboard shortcuts, as well as custom scripts to show tint2 on more general events.
This behavior could be enabled with a boolean setting in the configuration file (disabled by default for backward compatibility).
In the case the
autohide option is set to 0, SIGUSR2 acts as a simple bit flip. The starting state could be set with a second boolean option (
In the other case (
autohide = 1), SIGUSR2 should trigger a similar (but not identical) behavior to mouseenter:
- show tint2
- if receving SIGUSR2 while counting, restart the routine
- hide tint2 upon counter routine end