diff options
| author | Hristo Venev <[email protected]> | 2020-02-01 18:08:00 +0100 |
|---|---|---|
| committer | Simon Ser <[email protected]> | 2020-02-10 18:58:09 +0100 |
| commit | 7affe5c1bda53a2bb57295b7b6dbe4494e8c007b (patch) | |
| tree | d55e64c43a785f15c6abf77d1891bb9d70b3e529 /swaybar/status_line.c | |
| 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 'swaybar/status_line.c')
| -rw-r--r-- | swaybar/status_line.c | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/swaybar/status_line.c b/swaybar/status_line.c index 2a9e1da8..fb9271f8 100644 --- a/swaybar/status_line.c +++ b/swaybar/status_line.c @@ -85,6 +85,13 @@ bool status_handle_readable(struct status_line *status) { } } + json_object *float_event_coords; + if (json_object_object_get_ex(header, "float_event_coords", &float_event_coords) + && json_object_get_boolean(float_event_coords)) { + sway_log(SWAY_DEBUG, "Enabling floating-point coordinates."); + status->float_event_coords = true; + } + json_object *signal; if (json_object_object_get_ex(header, "stop_signal", &signal)) { status->stop_signal = json_object_get_int(signal); |