On 08 Jul 2003 08:31:49 +0200, Dominik Vogt wrote: > > On Tue, Jul 08, 2003 at 08:12:18AM +0200, Olivier Chapuis wrote: > > On Mon, Jul 07, 2003 at 09:37:54AM +0200, Dominik Vogt wrote: > > > On Mon, Jul 07, 2003 at 09:09:42AM +0200, Olivier Chapuis wrote: > > > > On Sun, Jul 06, 2003 at 02:12:54PM +0200, [EMAIL PROTECTED] wrote: > > > > > On Sun, Jul 06, 2003 at 07:24:33AM +0200, Olivier Chapuis wrote: > > > > > > On Sat, Jul 05, 2003 at 10:15:25PM +0200, [EMAIL PROTECTED] wrote: > > > > > > > It seems to work as mozilla set it and the good algo is choosen. > > > > (All KDE >= 2 and GNOME2 apps set this prop). > > > > > > > > > > By the way, should we implement _NET_WM_STATE_FULLSCREEN? > > > > > > > > > > Yes. I'd like to do it myself to gather some experience with the > > > > > ewmh code. > > > > > > > > > > > > > It seems that this start to work. But what about a FullScreen command > > > > which removes the decoration, MoveResize the window to the size > > > > of the screen and possibly put the window in a given layer: > > > > > > > > FullScreen [bool] [StayOnTop|layer x y] [size_hint_override] > > > > > > > > then we define defaults fvwm func: > > > > > > > > AddToFunc EWMHFullScreenOn I FullScreen On > > > > AddToFunc EWMHFullScreenOff I FullScreen Off > > > > > > > > which are called when needed by the ewmh code. > > > > > > I'd prefer doing this via a function. We have way too many move/ > > > resize/maximize functions already. The new ewmh code calls the > > > ResizeMoveMaximize command. > > > > > > > Yes. But I do not see how to restore the "initial" window state > > without a designed command (or an new Maximize flags) for fullscreen: > > > > AddToFunc EWMHFullScreenOn > > + I WindowStyle !Borders, !Title > > + I WindowStyle StaysOnTop > > + I Maximize ewmhiwa 100 100 > > > > AddToFunc EWMHFullScreenOff > > + I WindowStyle Borders, Title > > + I WindowStyle StaysPut > > + I Maximize off > > > > works well only on decorated stays put window. > > Again - use the ResizeMoveMaximize command. It does all you need > at the same time. I see no need to remove the window decorations. > Moving them off screen should suffice.
FullScreen should remove decorations, at least this is what a user expects. A window in the full screen mode should occupy only one page. A window occupying 9 pages (ResizeMoveMaximize) causes several problems. fvwm-themes has MaximizeFullScreen functions similar to the ones above for some years. Of course it uses Style $n to remove decorations, so there are often glitches (unrelated windows loosing decorations). The proper way to do this is using WindowStyle, not Style $n, of course. There are several other things in fvwm-themes that require WindowStyle. As for me, restoring the initial values of the layer and decorations is a bonus, but not very important, the functions similar to the ones above may be enough until 3.0. What is more important for 2.6 is WindowStyle. So a user has a full control on his windows individually, something that is possible in most of the other window managers. Returning to this thread, it is nice that we support both application move methods now. Nice work, Dominik. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
