On Fri, 12 Oct 2001, Mikhael Goikhman wrote:
> > 1. BorderWidth and NoHandles are accessible only in a Style command, and
> > Style is not permitted in a decor definition. (The man page says this,
> > somewhat indirectly, in the AddToDecor section---but the example given
> > contradicts that. Bug?). Fvwm complains, and effectively executes the
> > Style command immediately. (If I replace "StyleMaximized" with "*" then
> > all windows, maximized or not, lose their borders)
>
> There is no contradiction, please read a warning on the standard error.
> Fortunately or not, decors do not control border width; styles do.
I saw the warning. I should have been more clear; the contradiction was
that the man page implies that it is illegal to place a Style command
within an AddToDecor definition---and then proceeds to give two code
examples that do exactly that. To quote:
AddToDecor is similar in usage to the AddToMenu and
AddToFunc commands, except that menus and functions
are replaced by ButtonStyle, AddButtonStyle,
TitleStyle, AddTitleStyle and BorderStyle commands.
...versus...
The following example creates a decor "FlatDecor"
and style "FlatStyle". They are distinct entities:
AddToDecor FlatDecor
+ ButtonStyle All ActiveUp (-- flat) \
Inactive (-- flat)
+ TitleStyle -- flat
+ BorderStyle -- HiddenHandles NoInset
+ Style FlatStyle UseDecor FlatDecor, \
Color white/grey40,HandleWidth 4
...and...
AddToDecor FlatDecor
+ Style FlatStyle UseDecor FlatDecor, \
Color white/grey40,HandleWidth 4
Anyway, that's why I thought my StyleMaximized definition was valid at
first. Surely the above is a bug in the documentation, however small...?
> > 2. "Style" appears to be a bad way of implementing the "borderless
> > maximize" functionality, because its scope can only be specified by a
> > window name/class/resource---it cannot be applied to *one specific window*
> > and no other. If I maximize an XV window, say, and start up another XV
> > instance elsewhere, the second XV window should have borders!
>
> Yes, Style as we know it now does not help in 100% of cases. In the future
> there will be an ability to apply Style to individual windows.
Understood. "Style $w" would kill this issue completely.
> > 3. DecorMaximized, as given above, doesn't seem to inherit the effects of
> > the large number of "Style *" and other ____Style commands that precede
> > it. Right now, when I maximize a window, the window decorations take on a
> > distinctly uncustomized look. How do I make DecorMaximized inherit
> > everything from the Default decor?
>
> You can't inherit decors, you should recreate them from scratch or
> initialize like it is suggested in the link I posted 2 days ago.
Found it in the archives ... ooh, that's not pretty. IMHO, dropping decors
in favor of [a more generalized form of] styles seems like a good idea.
Chalk up some definite newbie confusion to the separation (or lack
thereof) between the two.
> > 4. Even if I jury-rig the first snippet of code to use "Style $n" to
> > assign "BorderWidth 0 ..." to the maximized window, the borderless window
> > does not fill the entire screen---it leaves a space at the right and
> > bottom edges that is twice the normal BorderWidth. Fvwm doesn't seem to be
> > taking into account the changed dimensions of the window. (Would some
> > invocation of Recapture do the trick here? How?)
>
> If you first remove borders and then Maximize, there should be no any gap
> for freely resizable windows. But you can't remove a gap for grid-like
> resizable windows like xterm, if you use font 7x14 you may have a gap up
> to 6 pixels at the right and up to 13 pixels at the bottom.
I got your other message on this, that an interposing UpdateStyles command
is needed. I should have mentioned that the above-mentioned gaps occurred
with XV as the test subject, but no matter now....
Thank you for your help! I look forward to making this work someday :)
Sincerely,
--Danny
Daniel Richard G.
<skunk_at_graphics.lcs.mit.edu>
MIT Computer Graphics Group
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Oct 11 2001 - 21:57:13 BST