> 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.
Both. cm, and netscape. As a hunch I went through all perumations of
OLDecor/NoOLDecor MWMFunctions/NoFuncHints MWMDecor/NoDecorHints
Remember, Close on button 2, Maximize on 4, Iconify on 6.
In Netscape, if the MWM ones are set, and there is a hint for no mix or
max button, there is no close button.
In cm, if OLDecor is set, no close button when there is no min or max
button.
>
> > 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.
Remember, old OLWM and OLVWM dont have "close" buttons. Its all off a
single pull down window menu. the cm transients do have a close in their
window ops pulldown.
>
> If you want the close button on all windows, tell fvwm2 to ignore the
> decor hints.
What if I want the decor hints, so that I dont get the icon and max
buttons on those windows that are hinted not to get them, but want the
close button.
>
> > 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...
As another hunch, I reordered the buttons. Putting close on button 6,
iconify on button 2.
Suddenly there is my close button. So I think the above may be where to
look. I also found a window with No Maximize set, but allowing iconify.
(netscape MWM hints) In this case, the Max and iconify buttons were noth
gone, which would make sense. Maximize on button 4 being "hinted out"
would prevent button 2 from being drawn.
>
> > (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.
Xterm
Style "*" MWMButtons
Maximize button does not stay sunk when window is maximized.
Yes, the MWMDecorMax is set for that button.
>
> > -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?
> > >
> >
> > --
>
--
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:40:32 GMT