Thanks for the clarification. Much appreciated. I'm interested in implementing a sub-surface example. Is a MR/PR of interest?
Thanks, Joel On Tue, Nov 1, 2022 at 1:53 AM Pekka Paalanen <ppaala...@gmail.com> wrote: > On Mon, 31 Oct 2022 10:14:42 -0700 > Joel Winarske <joel.winar...@gmail.com> wrote: > > > Thank you for the enlightenment! > > > > Adding the ordered commit calls was the missing link. > > > > Do the commit calls need to happen based on the active Z-order, or based > on > > the order of surface creation? > > They need to be ordered by sub-surface relationships, i.e. what is the > parent surface for a sub-surface. > > Z-order is completely irrelevant here. Also wl_surface creation order > is irrelevant. What is relevant is what you set as the parent > wl_surface in wl_subcompositor.get_subsurface request. > > You can create a sub-surface tree in any order by creating the > wl_subsurface objects in any order. The relevant thing is the final > parent surface <-> sub-surface association graph (actually a tree) when > you start doing updates (commits) to the wl_surfaces. > > > Thanks, > pq >
