On Tue, Jul 08, 2003 at 04:53:48PM +0000, Mikhael Goikhman wrote:
> On 08 Jul 2003 08:31:49 +0200, Dominik Vogt wrote:
> > 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.
I agree with parv that this should *at least* be configurable.
Moving the title bar off screen or even disabling it completely is
about the worst abuse of the power given to an application. In
many configurations this has the potential to make the desktop
totally unusable. Perhaps we should think of an emergency key
binding to disable the full screen state of all windows on the
current page.
> A window in the full screen mode should occupy only one page.
> A window occupying 9 pages (ResizeMoveMaximize) causes several problems.
I don't think anybody suggested that. I was talking about
Xinerama screens.
> 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.
There may be an easy way to achieve overriding styles for a
limited period of time. Add a field to the style structure that
can contain a unique style id. Then throw in a couple of
features:
StyleWithId <envvar> <Stylename> <Options>
Like Style, but assigns a unique id to the style and stores it
in the environment variable <envvar>. Styles with different
ids can not be merged. By default, all normal styles have the
id 0.
DestroyStyleId <id>
Destroys the style with the <id>.
Usage:
AddToFunc foo
+ I StyleWithId SID_$w $n HandleWidth 0, BorderWidth 0, NoTitle
and later:
ThisWindow DestroyStyleWithId $$[SID_$w]
(The ThisWIndow call is necessary to force expanding variables
twice - no idea how to do this in a functions.)
--
By the way, this idea shows nicely one of the shortcomings of a
WindowStyle command separate from the Style command. You'd have
to add the id functionality to both.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
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]
