<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: absolute mode for logogram input on a touchpad" href="https://bugs.freedesktop.org/show_bug.cgi?id=85879#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: absolute mode for logogram input on a touchpad" href="https://bugs.freedesktop.org/show_bug.cgi?id=85879">bug 85879</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>I don't think a frame event is needed here. The history of that is a bit blurry anyway, AIUI the frame stems largely from the MT protocol A in Qt, but with the protocol B the frame event is to some extent superfluous (still useful, but just not as needed). This interface is aimed primarily at single-finger interactions, so i think a frame event is unnecessary here though it could be added later. Renaming to libinput_event_touchpad sounds good, I'll do that in the next revision. (In reply to Jonas Ådahl from <a href="show_bug.cgi?id=85879#c8">comment #8</a>) > @@ +4954,5 @@ > > + * require changing to a neutral state first before activating the new > > + * method. > > + * > > + * Disabling the direct touch mode on a device that does not have a direct > > + * touch mode always succeeds. > > Should it be specified what happens to active gestures (including two finger > scroll, and tap) etc? Do they continue, or are they cancelled in some way? That's what the sentence just above should've clarified, unless the device is in a neutral state the mode won't activate yet. so any current ongoing gestures have to end before the mode is activated. I'll try to add/reword this</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>