In message <m0tGDUd-0008zNC_at_blunote>
sh_at_blunote.muc.de (Stefan Huebner) did scrawl:
>Later I discovered that a fvwm1-functionality has gone: You cannot use
>both the "Style IconBox" and "FvwmIconBox" anymore. This is because you
>have to apply 'Style "*" NoIcon' if you want so see icons in FvwmIconBox.
>In fvwm1 I used both icons on the desktop and in the Box !
This is an excerpt from my .fvwmrc, and it allows me to iconise FvwmButtons and
FvwmIconBox, and I'm sure I could specify other Icons!
Style "*" SloppyFocus, IconBox +0 -55 +100 -0, ForeColor Black, BackColor LightSkyBlue, MWMFunctions, HintOverride, MWMDecor, MWMButtons, SmartPlacement, NoPPosition, DecorateTransient, BorderWidth 5, HandleWidth 5, Color Black/#60a0c0, NoIcon
Style "Fvwm*" NoTitle, NoHandles, Sticky, WindowListSkip
Style "FvwmIconBox" Icon toolbox.xpm
Style "FvwmButtons" Icon toolbox.xpm
Style "Fvwm*" WindowListSkip
>A good solution to this problem could be to completely move the
>functionality of "Style IconBox" to FvwmIconBox. This could be done with
>*FvwmIconBox statements that allow one to
> - control the thickness of the border of FvwmIconBox
Style "FvwmIconBox" BorderWidth <..>
> - completely disable the border and scrollbars
Style "FvwmIconBox" BorderWidth 0
*FvwmIconBoxHideSC horizontal
*FvwmIconBoxHideSC vertical
> - disable the iconbox-background, so icons can be placed directly on the
> desktop-background
Just switch off FvwmIconBox and use:
Style "*" IconBox <top left x y> <bottom right x y>
> - an option that allows to control what icons are shown in the Iconbox
> (currently 'Style Iconbox' shows only iconified windows, FvwmIconBox
> shows all started x-apps and modules)
Style toolname Icon tool.xpm
*FvwmIconBox "toolname" -
>I also noticed that the order of statements is important in fvwm2.
Well known, and documented!!
>Let's say if you put 'Style "*" NoIcon' before any other 'Style "*" Icon
>foo' statement then no icons are displayed in the IconBox.
Of course, that how Styles work! (they're OR'd together)
>
>Other small problems with fvwm are:
>
>Sometimes I have timing problems when using swallow-programs in
>FvwmButtons. I had to insert wait-statements in the init- and restart-
>functions of the module, because sometimes the programs don't swallow but
>appear as normal windows. (Especially if I swallow commands like
>'rsh slowhost "xload -display local:0"')
So? What's the problem? Stick with the Waits.
>FvwmButtons is slow on my Pentium even with a PCI/VRAM graphics adapter.
>I use to display many colored icons in the module. The initilization is
>slow, and also when moving windows over the buttons-module the repaint is
>very slow.
Stop using PCs then! ;-) I have no problems with my Sparc 5!
Tara,
Ben.
| URL=
http://www.dcs.aber.ac.uk/~btk/ | email=btk_at_aber.ac.uk | _|--|_ o |
+-------------------------------------+----------------------+ (\/) +---+ |
| Tel: (01970) 622403 [Int: 2403] | or: (01970) 624165 | vv / \ |
--
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 Fri Nov 17 1995 - 07:58:48 GMT