[Wayland-bugs] [Bug 98731] EGL client behaviour too undefined

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Nov 15 03:59:21 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=98731

            Bug ID: 98731
           Summary: EGL client behaviour too undefined
           Product: Wayland
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: wayland
          Assignee: wayland-bugs at lists.freedesktop.org
          Reporter: jadahl at gmail.com

The behaviour of EGL clients is too undefined. For example when exactly a
client can expect wl_surface.attach+wl_surface.commit is not known, making it
hard to implement a well behaving client correctly. This is especially
problematic in combination with xdg_shell with version >= unstable v6, since it
is required that the first buffer attached to a surface must comply to the
requirements of the initial configure event.

For example, an application that does



surface = wl_compositor_create_surface();
egl_window = wl_egl_window_create(surface, some_width, some_height);
xdg_surface = xdg_shell_get_xdg_surface(surface);

--> on configure

wl_egl_window_resize(egl_window, actual_width, actual_height);
.. draw things ..
eglSwapBuffers()




may work on some EGL implementations, but not on others.

Some uncertainties that needs to be clarified:

1) When can wl_surface.attach be expected to take place
2) When can wl_surface.commit be expected to take place
3) What is the dimension of the wl_buffer used in 1) and 2)



Some requirements that needs to be met in order to guarantee a correct initial
frame (as required by the current xdg_shell version):

a) It must be possible to know when the buffer of the first frame is attached
and committed so that it is possible to set up the associated state (i.e.
windew geometry, input region, opaque region etc)
b) It must be possible to know when buffers of subsequent frames are attached
and commited so that is possible to set up the same set of associated state
(i.e. window geometry and input region when a surface is resized, or opaque
region when the content changes).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20161115/803184fa/attachment.html>


More information about the wayland-bugs mailing list