Looking at the Weston branch again I found some problems so I've force
pushed a new version.
I wasn't destroying the wl_buffer that the subcompositor creates with
eglCreateWaylandBufferFromImageWL when the client destroys its buffer.
This doesn't really matter because in this example the client do
Hi,
I think this thread has gotten a bit tangled so I've done a bit of minor
rebasing for the patches and pushed them all to github:
https://github.com/bpeel/wayland/commits/wip/wayland-subcompositor
https://github.com/bpeel/mesa/commits/wip/wayland-subcompositor
https://github.com/bpeel/weston/c
I wrote:
> • It seems to cause the nested-client to cycle between three buffers
> while rendering whereas previously it would only use two. I may have
> messed something up with the ordering between the frame callbacks and
> the buffer release events but I'm not sure yet.
I think I got to the bott
Hi,
Here is a series of patches to provide a way for a nested compositor to
present its clients using subsurfaces so that it can attach the client's
buffers directly to the subsurface without having to perform a blit to an
intermediate buffer.
The first patch is for Mesa which adds an extension c
