<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: Provide information about scroll devices"
href="https://bugzilla.gnome.org/show_bug.cgi?id=767093#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - wayland: Provide information about scroll devices"
href="https://bugzilla.gnome.org/show_bug.cgi?id=767093">bug 767093</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=mclasen%40redhat.com" title="Matthias Clasen <mclasen@redhat.com>"> <span class="fn">Matthias Clasen</span></a>
</span></b>
<pre>(In reply to Carlos Garnacho from <a href="show_bug.cgi?id=767093#c2">comment #2</a>)
<span class="quote">> 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.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>