Andrew Laden <andrew_at_sgc.com> writes:
> Ok. Cool. Getting closer.
>
> Using the info below, I can get rid of the iconify button on the
> transient.
>
> But the close button still doesnt show up.
Is that with "cm", or a Motif application? I can't verify this now,
but I think OLDecor would control the close button with "cm". In any
case, I think you are looking at the effect of enabling Open Windows
or Motif decor hints.
> So lets change the question. How can I get the close button to show up on
> those transient windows? I guess I could
>
> Style "*" NoDecorHint, NoFuncHint, NoOLDecor
>
> But thats throwing the baby out with the bathwater I think.
I think not.
Its a separate question as to why "cm" transients set the hint for no
close button and then don't supply a pulldown for close. I don't have
the answer for that, but found it useful to create a keybinding for
close. "dtcm" transients do have a pull down menu for close.
If you want the close button on all windows, tell fvwm2 to ignore the
decor hints.
> With the hints and functions on, fvwm seems to get rid of the close button
> if there are any other hints. Maybe its a location thing. If button 4 goes
> away, it takes away button 2 as well. If 6 goes away, it takes out 2 and
> 4. Etc.
As I remember this discussed years ago, it is a location thing. Right
now the actual logic in the source code is hiding from me...
> (BTW, Motif hints are reflected in the window menu. It greys out
> inappropriate selections. HintOverride allows you to select them anyway)
>
> Also, on a side note. The MWMButtons style doesnt seem to be working
> either.
Please report the application, your Motif settings in your .fvwm2rc
and the symptom.
> -Andrew
>
> --
>
> On 2 Feb 1999, Paul D. Smith wrote:
>
> > %% Andrew Laden <andrew_at_sgc.com> writes:
> >
> > al> 1: Decorating transients in Netscape 4.5 and others.
> >
> > al> Using netscape 4.5, with my decor set essentailly to the Windows
> > al> 95 look provided in the sample config files. Netscape
> > al> occasionally pops up secondary windows. Advertisements,
> > al> supplimental windows etc. These windows dont get all the buttons
> > al> that I have defined. In particular, they dont get button 2, which
> > al> is mapped to close. Its annoying, since thats what I usually want
> > al> to do with those windows. Its not greyed out in the menu, so there
> > al> is no "hint" blocking it.
> >
> > I think there is, though. I don't think the Motif hints are reflected
> > in the menu selections (how could they be?).
> >
> > al> However, the iconify and maximize are greyed out in some of them,
> > al> yet I still see the iconify button. Maybe there is some bug
> > al> between mapping what buttons should be hinted out vs what buttons
> > al> actually are?
> >
> > There's no bug, that's a feature! :)
> >
> > There's no way for FVWM to know which of the 7 (or whatever) buttons the
> > user defined should be ignored when the window hint for "can't iconify"
> > is set (for example).
> >
> > So, it chooses the Motif defaults; that is, for iconify or minimize, it
> > chooses the second to the right. Etc.
> >
> > If you want to tell FVWM that different buttons should take effect for
> > the different Motif hints, then see the ButtonStyle command, where you
> > can attach MWMDecorMenu, MWMDecorMin, and MWMDecorMax flags to the
> > appropriate buttons.
> >
> > I'm not sure if there's any way to get FVWM to ignore these hints
> > altogether? I guess if you turn off MWMFunctions?
> >
>
> --
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.bellcore.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Feb 02 1999 - 15:16:51 GMT