After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 767093 - wayland: Provide information about scroll devices
wayland: Provide information about scroll devices
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 753202
 
 
Reported: 2016-06-01 03:16 UTC by Matthias Clasen
Modified: 2016-06-01 18:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
wayland: Provide information about scroll devices (10.93 KB, patch)
2016-06-01 03:16 UTC, Matthias Clasen
committed Details | Review

Description Matthias Clasen 2016-06-01 03:16:46 UTC
The Wayland protocol does not share XI2's wealth of information
about individual devices, but it does provide discriminating
information about sources for scroll events. Pass this on to
the application by creating separate slave devices for these,
and setting them as source device on the scroll events.
Comment 1 Matthias Clasen 2016-06-01 03:16:50 UTC
Created attachment 328854 [details] [review]
wayland: Provide information about scroll devices
Comment 2 Carlos Garnacho 2016-06-01 12:07:02 UTC
The approach looks fine to me, I guess it's worth pointing out though that one physical device may have >1 scroll methods (eg. mouse with wheel and a scroll button assigned).

I guess this is mostly up to the compositor offering such level of configurability, so this combination of features is sounds unlikely enough (not like they make a lot of sense together either). I think it's just fine to possibly send scroll events from two source devices in those cases.
Comment 3 Matthias Clasen 2016-06-01 13:10:15 UTC
(In reply to Carlos Garnacho from comment #2)
> The approach looks fine to me, I guess it's worth pointing out though that
> one physical device may have >1 scroll methods (eg. mouse with wheel and a
> scroll button assigned).
> 
> I guess this is mostly up to the compositor offering such level of
> configurability, so this combination of features is sounds unlikely enough
> (not like they make a lot of sense together either). I think it's just fine
> to possibly send scroll events from two source devices in those cases.

Yeah. Whats a 'single device' is a bit in the eye of the beholder anyway. E.g. I as a user think of the buttons above my touchpad as part of the touchpad, but the hw thinks they belong to the nipple.
Comment 4 Matthias Clasen 2016-06-01 18:53:45 UTC
Attachment 328854 [details] pushed as 3d0f768 - wayland: Provide information about scroll devices