On Wed, Jun 07, 2006 at 06:17:36AM -0400, Geoffrey Alan Washburn wrote:
> Anselm R. Garbe wrote:
> >On Wed, Jun 07, 2006 at 11:49:08AM +0200, Stefan Tibus wrote:
> >
> >>On Wed, Jun 07, 2006 at 11:24:14AM +0200, Anselm R. Garbe wrote:
> >>
> >>>wmii treats applications
> >>>which windows request the size of the display as fullscreen
> >>>apps, which are always floating.
> >>>
> >>Does this mean that a managed application with a single window in
> >>the corresponding view will be floating the next time when it
> >>stores the size (fullscreen, as it was the only window) on quit
> >>and requests that one again on start-up?
> >>
> >
> >If a window requests exactly screen size, it will be floating
> >and cover the screen (this has to be done to support
> >fullscreen-windows like mplayer, xpdf -fullscreen etc.).
> >
>
> This doesn't seem like the correct behavior. ion3 doesn't seem to
> have any problems distinguishing between the case when an application
> wants the full screen and when it asks for a window the size of a full
> screen (in which case it ignores it).
The difference is, wmii does not ignore such windows. It handles
them in the same way. wmii only ignores override_redirect'ed
windows. If a window requests screen size it gets screen size
and its border gets invisible. To me there is nothing wrong with
this behavior.
> >No, but it's simple:
> >
> >A new window will be floating,
> > - if it inherits the current tag AND the floating layer is focused
> >OR
> > - if an associated ~-rule matches the windows class:instance or name
> >OR
> > - if it has set the WM_TRANSIENT_FOR hint, it inherits the
> > tag of the main window and will be floating
OR
- it requests screen size
OR
- it requests a fixed size (in wmii-3.1+)
> But this seems to contradict what you just said above.
I clarified things...
Regards,
--
Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361
_______________________________________________
[email protected] mailing list
http://wmii.de/cgi-bin/mailman/listinfo/wmii
