On Sep 25, 2014 3:04 PM, "Jasper St. Pierre" <<a href="mailto:jstpierre@mecheye.net">jstpierre@mecheye.net</a>> wrote: > > > > On Thu, Sep 25, 2014 at 3:58 PM, Bill Spitzak <<a href="mailto:spitzak@gmail.com">spitzak@gmail.com</a>> wrote: >> >> On 09/25/2014 01:57 PM, Jasper St. Pierre wrote: >> >>> <a href="https://github.com/magcius/weston/commit/c1e5a846f4f57400bca1262111f9793e451c5b49">https://github.com/magcius/weston/commit/c1e5a846f4f57400bca1262111f9793e451c5b49</a> >> >> >> That patch has nothing to do with what is needed. >> >> You don't need a "modal window type". This is trivial for a client to do by just pretending that whatever keystrokes it gets go to the "modal" window even if the compositor sends them to a different window. >> >> What is needed is a non-flickering and atomic method of creating that modal window atop the main one and keeping it there. That requires a parent, not a "modal" flag. (well actually it does not require a parent if instead there was a way to atomically map and rearrange a set of surfaces, but I think the parent will be much easier and matches what programmers are familiar with). > > > You mean like the existing set_parent request that has been there since xdg-shell has landed? > > <a href="http://cgit.freedesktop.org/wayland/weston/tree/protocol/xdg-shell.xml#n140">http://cgit.freedesktop.org/wayland/weston/tree/protocol/xdg-shell.xml#n140</a> If parenting isn't sufficient, it would be easy enough to add a mutter extension for modal windows in the form of another state enum. If it turns out to be a well-defined thing other compositors want, we can think about moving it to core. In any case, it should be trivial from a protocol point of view. > > -- > Jasper > > _______________________________________________ > wayland-devel mailing list > <a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a> >