<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed" href="https://bugzilla.gnome.org/show_bug.cgi?id=753185#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed" href="https://bugzilla.gnome.org/show_bug.cgi?id=753185">bug 753185</a> from <a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> Carlos Garnacho</a> <pre>(In reply to Matthias Clasen from <a href="show_bug.cgi?id=753185#c2">comment #2</a>) > Not holding on to pointers that point to finalized objects seems good, of > course. But can we recognize the 'deceased' status of the devices somehow ? > Is there a GdkDevice api for that ? Hmm, right, there's actually nothing to let users know. On X11 I'd count on BadDevice to be received on any device operation, and GTK+ to bail out of there, on wayland this post-removal behavior is a bit more naive though. What AFAIR we would be emitting is grab broken events if there is one at the time of the removal, and I wouldn't expect that button/key releases will trigger grabs or device state queries too often, We should stress test device operations around removals nonetheless.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>