summaryrefslogtreecommitdiff
path: root/gdk/wayland/gdkeventsource.c
Commit message (Collapse)AuthorAgeFilesLines
* Handle recursion from motion event handlersOwen W. Taylor2013-11-111-2/+2
| | | | | | | | | | | | If a motion event handler (or other handler running from the flush-events phase of the frame clock) recursed the main loop then flushing wouldn't complete until after the recursed main loop returned, and various aspects of the state would get out of sync. To fix this, change flushing of the event queue to simply mark events as ready to flush, and let normal event delivery handle the rest. https://bugzilla.gnome.org/show_bug.cgi?id=705176
* wayland: Dispatch pending events before entering pollRob Bradford2013-08-041-0/+3
| | | | | | If we don't dispatch the pending events then we can enter poll with events still requiring to be processed and which can then lead to us deadlocking there.
* wayland: Handle the display connection erroring outRob Bradford2013-07-091-2/+8
| | | | | | | wl_display_flush or wl_display_dispatch can return -1 if there is an error on the display connection. https://bugzilla.gnome.org/show_bug.cgi?id=703892
* wayland: Don't clear revents until we've checked for G_IO_HUPKristian Høgsberg2013-07-091-4/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=703892
* wayland: Don't error out on G_IO_HUP until we've read G_IO_IN dataKristian Høgsberg2013-03-301-4/+4
| | | | | | We can get G_IO_HUP and G_IO_IN at the same time, if the compositor writes data to us and then closes our connection. Make sure that we dispatch events always if we have G_IO_IN and then error out if we get G_IO_HUP after that.
* wayland: don't attempt to unqueue events when events are pausedThomas Wood2013-02-211-0/+6
| | | | | | | | | | | When events are paused, we should not return TRUE from prepare() or check(). GTK+ handles this for events that are already in the GTK+ queue, but we also need suppress checks for events that are in the system queue - if we return TRUE indicating that there are events in the system queue, then we'll call dispatch(), and do nothing. The event source will spin, and will never run the other phases of the paint clock. https://bugzilla.gnome.org/show_bug.cgi?id=694274
* wayland: React to G_IO_ERR and G_IO_HUP on the wayland socketRob Bradford2013-02-061-1/+4
| | | | Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=692728
* wayland: Update to reflect protocol changesScott Moreau2012-10-191-27/+4
|
* gdk: Don't use GDK_THREADS_ENTER/LEAVE macros internallyMatthias Clasen2012-07-301-2/+2
| | | | | | These are just wrappers for the functions, and we want to deprecate them. Stopping to use them internally is a good first step.
* wayland: Rename GdkDisplayWayland to GdkWaylandDisplayRob Bradford2012-04-171-6/+6
| | | | | This makes it consistent with the functions in the vtable and also consistent with other backends.
* Change FSF AddressJavier Jardón2012-02-271-3/+1
|
* wayland: Make the event source use _gdk_display_get_next_serialRob Bradford2012-01-061-2/+2
|
* wayland: Support setting cursorsKristian Høgsberg2011-02-091-1/+1
| | | | | And a handful unrelated cleanups. Still doesn't really have an answer for cursor themes.
* Dont iterate the display if there's nothing to writeKristian Høgsberg2011-02-051-0/+10
|
* Add Wayland backendKristian Høgsberg2011-02-051-0/+167
View Lorry Controller Status