aboutsummaryrefslogtreecommitdiff
path: root/sway/sway-output.5.scd
diff options
context:
space:
mode:
authorJoan Bruguera <joanbrugueram@gmail.com>2021-09-18 22:21:22 +0200
committerSimon Ser <contact@emersion.fr>2022-11-26 10:17:53 +0100
commit94b69acf0d7b26ee5af2172300cb18473508da76 (patch)
tree1b26242344968929fc2698b49b12478eb9fe4fae /sway/sway-output.5.scd
parent53f9dbd424dc173a85c9f4cd30802259d38b1ef4 (diff)
swaybar: Make hotspots block bar release bindings
The previous commit prioritized hotspots before bar bindings for press events, which matches i3's behaviour. However, since hotspots don't need to do any processing on release events, those were not handled, and simply fell through to `bindsym --release` bar bindings (if any). This is counter-intuitive, and doesn't match i3's behaviour. Instead in case a hotspot handles the press event, it should also handle the release event, doing nothing, but blocking the event from triggering a --release bar binding. E.g., in Sway, without this commit, this config. shows a text on tray clicks: bar { # ... bindsym --release button1 exec swaynag -m I_got_the_release_event. } But the same configuration in i3 (with i3-nagbar) doesn't show the text. Signed-off-by: Joan Bruguera <joanbrugueram@gmail.com>
Diffstat (limited to 'sway/sway-output.5.scd')
0 files changed, 0 insertions, 0 deletions