On Wed, Apr 23, 2003 at 10:36:30PM +0200, [EMAIL PROTECTED] wrote: > On Wed, Apr 23, 2003 at 09:24:21PM +0200, Yves Salathe wrote: > > > > Hi > > > > Recently I wrote this little patch for FvwmButtons so that it now > > understands the [EMAIL PROTECTED] geometry option. There may be better > > solutions > > but it seems to work. I hope that helps. > > But it already has support for '@screen' built in. You patched > the code determining the placement of the buttons inside the > button bar. With your patch you can now specify > > *FvwmButtons([EMAIL PROTECTED], Tile foo, ...) > > ?! What would that be good for?
I'm not sure what you mean. I think there are two ways to specify the size and position of FvwmButtons: 1. *FvwmButtons: Geometry [EMAIL PROTECTED] 2. *FvwmButtons: ButtonGeometry [EMAIL PROTECTED] The second attempt specifies only the size of one Button while the first attempt specifies the size of the whole window. But the position part of the geometry works the same way in both cases. In parse.c the two attempts both modify UberButton which doesn't seem to be a true button but its coordinates set the position of the window in the function CreateUberButtonWindow in FvwmButtons.c. The size of UberButton is only 1 or 0 and it seems to indicate whether or not the coordinates are negative. Negative coordinates mean for example south west gravity. FvwmButtons does not natively support '@screen' in these configuration options. Please correct me if I'm wrong. Bye Yves -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
