From 0a9b468540d4be7dbea3b63515b64eaa5c187f0f Mon Sep 17 00:00:00 2001 From: Joan Bruguera Date: Sat, 18 Sep 2021 22:21:22 +0200 Subject: 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 (cherry picked from commit 94b69acf0d7b26ee5af2172300cb18473508da76) --- include/swaybar/input.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'include/swaybar/input.h') diff --git a/include/swaybar/input.h b/include/swaybar/input.h index e8735d88..8ea88a69 100644 --- a/include/swaybar/input.h +++ b/include/swaybar/input.h @@ -49,7 +49,7 @@ struct swaybar_hotspot { int x, y, width, height; enum hotspot_event_handling (*callback)(struct swaybar_output *output, struct swaybar_hotspot *hotspot, double x, double y, uint32_t button, - void *data); + bool released, void *data); void (*destroy)(void *data); void *data; }; -- cgit v1.2.3-70-g09d2