On Mon, May 02, 2016 at 04:42:52PM +0300, Pekka Paalanen wrote: > On Mon, 2 May 2016 12:49:04 +0200 > Armin Krezović <[email protected]> wrote: > > > So, the backends should indicate to the compositor (and thence to the > > > enabled shell) that the output change has occurred, and then the shell > > > has the responsibility to rearrange the client surfaces as it wishes. > > > Perhaps you'd like to focus your scope on the backend side of things, > > > make sure the communication path *to* the shell is all working, but > > > leave the layout logic as outside scope to be done as followup work. > > > > > > > I think that desktop-shell already supports rendering on multiple outputs > > (as confirmed by plugging in a second monitor) and stopping any rendering > > from a certain output when it gets removed. It still needs to properly > > handle > > screen blanking and screensaver when all outputs are gone. The things will > > change when I start working on second part of my GSoC, which involves > > extended screens. > > Seems like you are talking about weston-desktop-shell the client. > Indeed, fairly easy to confirm with e.g. the x11-backend by letting > Weston create more than one X11 window. > > I forget if it was the Weston core or desktop shell plugin that > triggers blanking and powersave, and screensaver was removed some time > ago.
Blanking and powersave is all in Weston core. The fade in/out animation stuff is in the desktop shell. Bryce _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
