You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
And I just found the culprit: GTK doesn't do the kinetic thing if you send a wl_pointer.frame in between the wl_pointer.axis_stops!!
Silly workaround:
--- i/types/seat/wlr_seat_pointer.c+++ w/types/seat/wlr_seat_pointer.c@@ -264,10 +264,12 @@ void wlr_seat_pointer_send_axis(struct wlr_seat *wlr_seat, uint32_t time,
wl_pointer_send_axis(resource, time, orientation,
wl_fixed_from_double(value));
+ pointer_send_frame(resource);
} else if (version >= WL_POINTER_AXIS_STOP_SINCE_VERSION) {
wl_pointer_send_axis_stop(resource, time, orientation);
+ if (orientation > 0)+ pointer_send_frame(resource);
}
- pointer_send_frame(resource);
}
}
I'm not sure what would be the "beautiful" code to solve this. Weston just explicitly handles horizontal and vertical in the same function instead of having an orientation parameter.
The text was updated successfully, but these errors were encountered:
Frame events group logically connected pointer events. It makes sense to make
the backend responsible for sending frame events, since once the events are
split (ie. once the frame events are stripped) it's not easy to figure out
which events belongs to which frame again.
This is also how Weston handles frame events.
Fixesswaywm#1468
Frame events group logically connected pointer events. It makes sense to make
the backend responsible for sending frame events, since once the events are
split (ie. once the frame events are stripped) it's not easy to figure out
which events belongs to which frame again.
This is also how Weston handles frame events.
Fixesswaywm/wlroots#1468
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I can't believe there's no issue for this yet..
And I just found the culprit: GTK doesn't do the kinetic thing if you send a
wl_pointer.frame
in between thewl_pointer.axis_stop
s!!Silly workaround:
I'm not sure what would be the "beautiful" code to solve this. Weston just explicitly handles horizontal and vertical in the same function instead of having an orientation parameter.
The text was updated successfully, but these errors were encountered: