questions about gtk simple applications running on wayland
Zhao, Juan J
juan.j.zhao at intel.com
Fri Oct 28 08:01:55 PDT 2011
> -----Original Message-----
> From: wayland-devel-bounces+juan.j.zhao=intel.com at lists.freedesktop.org
> [mailto:wayland-devel-bounces+juan.j.zhao=intel.com at lists.freedesktop.org]
> On Behalf Of Tiago Vignatti
> Sent: Friday, October 28, 2011 8:54 PM
> To: wayland-devel at lists.freedesktop.org
> Subject: Re: questions about gtk simple applications running on wayland
> On 10/28/2011 03:19 PM, Zhao, Juan J wrote:
> > Updates today:
> > In the client side: Gtk call wl_egl_pixmap_create_buffer to create the
> > buffer and then use wl_surface_attach to attach this buffer to its surface.
> > In the server side: drm_create_buffer is called and add that buffer
> > resource to this client. And wl_map_insert_at will be called. That
> > buffer resource is inserted to the map. Then surface_attach will be
> > called, this buffer will be saved to one wlsc_surface.
> > Then in the client side, gtk call wl_shell_set_toplevel,
> > wl_connection_vmarshal will be called.
> > In the server side, shell_set_toplevel is called. The third parameter is
> > the previous buffer object created by drm_create_buffer not the
> > wlsc_surface.
> > Should I need to look into wl_connection_vmarshal to check each
> > parameter sent to the server?
> Are you sure this is happening only with GTK clients? Have you tried to
> isolate the problem, seeing if the same happens with the demo clients?
Yes, I'm sure it only happens for GTK clients only, the other clients can work well.
More information about the wayland-devel