On 06 Dec 2004 10:11:07 +0100, Olivier Chapuis wrote: > > On Sun, Dec 05, 2004 at 07:44:40PM -0500, Dan Espen wrote: > > > > For FvwmIconMan, I adjusted the first paragraph, but got stuck on the > > second: > > > > .IP "*FvwmIconMan: [id] MaxButtonWidth \fIwidth\fP" > > Defines a maximum for the width of a button (in pixels). By default there > > is no maximum. A value of 0 resets the default. The maximum is only used > > with a non growing manager (the ManagerGeometry option > > specifies non zero width and height). > > > > .IP "*FvwmIconMan: [id] MaxButtonWidthByColumns \fIcol\fP" > > This is equivalent to MaxButtonWidth ManWidth/col where ManWidth is > > the width of the Manager. > > > > > > What is "ManWidth"? > > > > Should this be "MaxWidthInColumns", or just "MaxColumns"? > > ManWidth is the width of the full FvwmIconMan. For example if the > width of the FvwmIconMan manager is 1024, "MaxButtonWidthByColumns 4" > is equivalent to "MaxButtonWidth 256". This is useful when you do not > know, at config time, the width of the manager (e.g., for swallowed > IconMan). In a certain sense you will never have less than 4 columns. > So maybe, MinColumns is good. I used MaxButtonWidthByColumns to say > that the MaxButtonWidth is expressed in terms of columns (or computed > from a number of columns. I like the idea to use something like > MaxButtonWidth_something_good to express the fact that this option > is just an other way to set the MaxButtonWidth option.
I think, "MinColumns" name is more intuitive. You should probably mention that setting "MinColumns" disables "MaxButtonWidth" (or vice versa), so it would be clear that they describe more or less the same thing. Regards, Mikhael. -- 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]
