On Sun, May 27, 2012 at 2:02 PM, Giovanni Campagna <scampa.giova...@gmail.com> wrote: > 2012/5/27 Michele Gaio <mic...@gmail.com>: >> No, for me the problem is not affectsStruts parameter, but >> visibleInFullscreen. Is the latter if set to false supposed to allow >> fullscreen windows to cover the actor? I've tried playing with it >> after reading Alberto's message, but I can't get the behaviour he is >> experiencing. > > visibleInFullscreen affects only the visibility of actors when a > window is fullscreen. The actual stacking of them is controlled by > clutter, so you would do "actor.raise_top()" to make it above > global.window_group (the actor holding the windows), and > "actor.lower_bottom()" to do the opposite. > Struts are not relevant to fullscreen, as they affect the workarea, > not the screen.
Gah, I read the constraints code wrong. I thought struts worked on full-screen. > Also note that if you have a reactive actor (that is, one with > affectInputRegions: true), the input region will be above everything > regardless of where the actor is placed, because at X11 level, your > actor is part of the XComposite overlay window. > > Giovanni > >> On 27 May 2012 19:35, Jasper St. Pierre <jstpie...@mecheye.net> wrote: >>> You're saying it doesn't affect struts. >>> >> _______________________________________________ >> gnome-shell-list mailing list >> gnome-shell-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/gnome-shell-list -- Jasper _______________________________________________ gnome-shell-list mailing list gnome-shell-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-shell-list
