mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-16 21:50:34 +00:00
76922c169f
Weston releases buffers almost immediately after they're done, which means that GTK+ doesn't use a temporary surface and instead paints directly onto the SHM backing store that Weston will use. Normally, after painting to the temporary surface, GTK+ *replaces* the existing backing surface with CAIRO_OPERATOR_SOURCE. However, if we immediately paint to the backing surface, it might have junk from the last paint in it. So clear out the backing surface whenever somebody calls begin_paint_region(). Maybe we should just always use the temporary surface like the X11 codepath, since that prevents us from having to do weird things like this, but oh well. |
||
|---|---|---|
| .. | ||
| 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 | ||
| wm-button-layout-translation.c | ||
| wm-button-layout-translation.h | ||