<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - popup windows don't get touch events" href="https://bugzilla.gnome.org/show_bug.cgi?id=750845#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - popup windows don't get touch events" href="https://bugzilla.gnome.org/show_bug.cgi?id=750845">bug 750845</a> from <a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> Carlos Garnacho</a> <pre>Created <a href="attachment.cgi?id=315892&action=diff" name="attach_315892" title="wayland: Separate touch pointer emulation into its own master pointer">attachment 315892</a> <a href="attachment.cgi?id=315892&action=edit" title="wayland: Separate touch pointer emulation into its own master pointer">[details]</a> <a href='review?bug=750845&attachment=315892'>[review]</a> wayland: Separate touch pointer emulation into its own master pointer The common GDK code accounts for "pointer emulating" touch sequences to be synchronized with the pointer position by the windowing system. However on Wayland pointer and touch are completely independent, the backend attempts to implement pointer emulation, but doesn't account for the possible crossing events happening when the user switches from pointer to touch or the opposite. In order to fix this, and to ensure we don't have to interact with the master pointer (which backs the wl_pointer), separate the touch interface to have its own master pointer, and ensure crossing events are emitted on it, so the picture of an "emulated pointer" is complete above the backend. Inspired in a former patch by Jonny Lamb <<a href="mailto:jonnylamb@gnome.org">jonnylamb@gnome.org</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>