Below is the case where I'm getting stuck with the actual test case. Wondering why there is no callback [email protected] or [email protected] The EGL implementation depends on these callback/buffer release. Also noticed if the valid buffer is attached immediately after null buffer, everything is fine, so most of the time it is unnoticed. If the frame is complex, egl will attach after null frame.
I will keep debug if any other race conditions in my implementation. [3741557.293] -> [email protected](new id wl_callback@25) [3741557.476] -> [email protected](wl_buffer@29, 0, 0) [3741557.676] -> [email protected](0, 0, 800, 480) [3741557.906] -> [email protected]() <=EGL [3741558.500] -> [email protected](nil, 0, 0) <=QTWayland [3741558.604] -> [email protected]() <=QTWayland stuck On Fri, Aug 21, 2015 at 12:16 PM, Jasper St. Pierre <[email protected]> wrote: > We need to fix that documentation, then, along with fixing Weston. > mutter will give you an error with this event stream, since attaching > a NULL buffer for an xdg_surface is invalid. > > This behavior is one of the reasons why I removed this ability from > xdg_surface and instead made it an error -- the semantics were > extremely unclear, and practically the same as destroying and > recreating the xdg_surface. Please do that instead. > > However crazy it is, the logic sort of makes sense -- the "frame" > event is guaranteed to be called once a frame when the surface content > is painted and shown on the screen. When there's no surface content, > it isn't painted, so the frame event isn't called. > > I'm not sure what you mean about a buffer release event -- you never > attached a buffer to begin with, so I can't imagine how you'll get an > event on it. > > On Fri, Aug 21, 2015 at 10:03 AM, Prabhu S <[email protected]> wrote: > > Hi, > > Based on the wayland protocol specification for wl_surface::attach > >>>If wl_surface.attach is sent with a NULL wl_buffer, the following > >>> wl_surface.commit will remove the surface content. > > > > Wondering if wl_surface_attach called with wl_buffer=NULL, will there be > any > > wl_buffer release event or frame callbacks? > > > > Modified the redraw in simple-shm.c as below and not receiving any > callback > > or buffer release. It just got stuck. > > The same thing is being done in qtwayland to hide the surface and it is > > getting stuck. Some help to check this case would be helpful. > > > > static int odd = 1; > > if(odd == 1){ > > wl_surface_attach(window->surface, buffer->buffer, 0, 0); > > wl_surface_damage(window->surface, > > 20, 20, window->width - 40, window->height - > 40); > > odd = 0; > > } > > else{ > > wl_surface_attach(window->surface, 0, 0, 0); > > wl_surface_damage(window->surface, > > 0, 0, 0, 0); > > odd=1; > > } > > > > > > > > [823379.816] -> [email protected]_surface(new id wl_surface@3) > > [823379.949] -> [email protected]_xdg_surface(new id xdg_surface@7, > > wl_surface@3) > > [823380.120] -> [email protected]_title("simple-shm") > > [823380.244] -> [email protected](0, 0, 250, 250) > > [823381.333] -> [email protected]_pool(new id wl_shm_pool@8, fd 5, > 250000) > > [823381.561] -> [email protected]_buffer(new id wl_buffer@9, 0, 250, > > 250, 1000, 1) > > [823381.870] -> [email protected]() > > [823384.880] -> [email protected](wl_buffer@9, 0, 0) > > [823385.095] -> [email protected](20, 20, 210, 210) > > [823385.317] -> [email protected](new id wl_callback@10) > > [823385.443] -> [email protected]() > > [823388.852] [email protected]_id(8) > > [823388.979] [email protected](0, 0, array, 4) > > [823389.238] -> [email protected]_configure(4) > > [823401.773] [email protected]_id(10) > > [823401.908] [email protected]() > > [823401.991] [email protected](4056537) > > [823404.239] -> [email protected](nil, 0, 0) > > [823404.442] -> [email protected](0, 0, 0, 0) > > [823404.663] -> [email protected](new id wl_callback@10) > > [823404.792] -> [email protected]() > > [823406.292] [email protected](0, 0, array, 5) > > [823406.524] -> [email protected]_configure(5) > > > > > > _______________________________________________ > > wayland-devel mailing list > > [email protected] > > http://lists.freedesktop.org/mailman/listinfo/wayland-devel > > > > > > -- > Jasper >
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
