forked from AuroraMiddleware/gtk
8061df1544
We can't destroy buffers if they're in-use by the compositor. Well, technically we can, but that is considered undefined by Wayland and mutter won't cope with it very well -- it simply kills the client. To solve this, we need to delay the destroy operation until the compositor tells us that it's released the buffer. To do this, hold an extra ref on the cairo surface as long as the surface is in-use by the compositor. |
||
|---|---|---|
| .. | ||
| protocol | ||
| gdkapplaunchcontext-wayland.c | ||
| gdkcursor-wayland.c | ||
| gdkdevice-wayland.c | ||
| gdkdisplay-wayland.c | ||
| gdkdisplay-wayland.h | ||
| gdkdnd-wayland.c | ||
| gdkeventsource.c | ||
| gdkkeys-wayland.c | ||
| gdkprivate-wayland.h | ||
| gdkscreen-wayland.c | ||
| gdkselection-wayland.c | ||
| gdkwayland.h | ||
| gdkwaylanddevice.h | ||
| gdkwaylanddisplay.h | ||
| gdkwaylandselection.h | ||
| gdkwaylandwindow.h | ||
| gdkwindow-wayland.c | ||
| Makefile.am | ||