https://bugs.freedesktop.org/show_bug.cgi?id=78372
--- Comment #4 from Pekka Paalanen <[email protected]> --- (In reply to comment #3) > Suppose a situation of 3 hardware overlays, with current wayland model if I > want to run data visualization app which uses these three overlays. And > application has parent window with first overlay, second and third overlays > are "not" child windows.Then how can I make my app structured correctly > graphically. It is up to the compositor to assign wl_surfaces into hw overlays any way it sees fit. It is not driven from clients. All a client is expected to do is to use a separate wl_surface for each thing that might be suitable for a hw overlay. If you need to glue several wl_surfaces together to form a single window to do this, use sub-surfaces (wl_subcompositor). > And is there any significance of not letting client choose their window > position on screen. Yes. A client cannot know what is on screen, so there is no way it could reasonably decide where to put its own windows. It is also much easier for the protocol by avoiding a lot traffic and interfaces, and it allows compositors to use arbitrary input/output redirection. > Is there any way to move window just after creating it? Not from a client. Moving a window is an interactive user action, or a window manager decision. > Do shell protocol have such functionality? No. We are assuming wl_shell or xdg_shell here, and not some other shell, right? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
