https://bugzilla.gnome.org/show_bug.cgi?id=771553
Jonas Ådahl <jad...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #335733|none |needs-work
status| |
--- Comment #5 from Jonas Ådahl <jad...@gmail.com> ---
Review of attachment 335733:
I'm sad to say I don't think this is the correct solution. The reason for this
is that we may end up with one incorrect frame (the one committed by
eglSwapBuffers()), that'll then be fixed up by setting the rest of the state
(window geometry, opaque region, etc) in the another commit (the one in
on_frame_clock_after_paint()).
What exactly is it in on_frame_clock_after_paint() that makes the issue go
away? Is it the gdk_wayland_window_sync_...() calls? I think those could
probably be safely moved to gdk_window_impl_wayland_end_paint().
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
