aboutsummaryrefslogtreecommitdiffstats
path: root/swaybar/tray
diff options
context:
space:
mode:
authorLibravatar Hristo Venev <hristo@venev.name>2020-02-01 18:08:00 +0100
committerLibravatar Simon Ser <contact@emersion.fr>2020-02-10 18:58:09 +0100
commit7affe5c1bda53a2bb57295b7b6dbe4494e8c007b (patch)
treed55e64c43a785f15c6abf77d1891bb9d70b3e529 /swaybar/tray
parentDo not truncate pointer coordinates to int. (diff)
downloadsway-7affe5c1bda53a2bb57295b7b6dbe4494e8c007b.tar.gz
sway-7affe5c1bda53a2bb57295b7b6dbe4494e8c007b.tar.zst
sway-7affe5c1bda53a2bb57295b7b6dbe4494e8c007b.zip
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/tray')
-rw-r--r--swaybar/tray/item.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/swaybar/tray/item.c b/swaybar/tray/item.c
index 06a8e5b0..b4238417 100644
--- a/swaybar/tray/item.c
+++ b/swaybar/tray/item.c
@@ -377,7 +377,7 @@ static int cmp_sni_id(const void *item, const void *cmp_to) {
377 377
378static enum hotspot_event_handling icon_hotspot_callback( 378static enum hotspot_event_handling icon_hotspot_callback(
379 struct swaybar_output *output, struct swaybar_hotspot *hotspot, 379 struct swaybar_output *output, struct swaybar_hotspot *hotspot,
380 int x, int y, uint32_t button, void *data) { 380 double x, double y, uint32_t button, void *data) {
381 sway_log(SWAY_DEBUG, "Clicked on %s", (char *)data); 381 sway_log(SWAY_DEBUG, "Clicked on %s", (char *)data);
382 382
383 struct swaybar_tray *tray = output->bar->tray; 383 struct swaybar_tray *tray = output->bar->tray;