diff options
| author | Hristo Venev <hristo@venev.name> | 2020-02-01 18:08:00 +0100 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2020-02-10 18:58:09 +0100 |
| commit | 7affe5c1bda53a2bb57295b7b6dbe4494e8c007b (patch) | |
| tree | d55e64c43a785f15c6abf77d1891bb9d70b3e529 /include/swaybar/input.h | |
| parent | fca32b6334afe69ea10c88de7670c79ae98ce0fd (diff) | |
swaybar: fix i3bar relative coordinates when scaling is used
24e8ba048aef4751c6fa1d5982ee634f921e6cf6 did not take scaling into account.
The hotspot size used pixel coordinates, the absolute coordinates were logical,
and the relative coordinates were completely wrong.
This commit makes all coordinates use logical values. If
`"float_event_coords":true` is sent in the handshake message, coordinates are
sent as floating-point values.
The "scale" field is an integer containing the scale value.
Diffstat (limited to 'include/swaybar/input.h')
| -rw-r--r-- | include/swaybar/input.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/swaybar/input.h b/include/swaybar/input.h index 6557a29e..65e49218 100644 --- a/include/swaybar/input.h +++ b/include/swaybar/input.h @@ -44,7 +44,7 @@ struct swaybar_hotspot { struct wl_list link; // swaybar_output::hotspots int x, y, width, height; enum hotspot_event_handling (*callback)(struct swaybar_output *output, - struct swaybar_hotspot *hotspot, int x, int y, uint32_t button, + struct swaybar_hotspot *hotspot, double x, double y, uint32_t button, void *data); void (*destroy)(void *data); void *data; |