On Thu, Apr 24, 2003 at 06:47:22PM +0200, Yves Salathe wrote:
> On Wed, Apr 23, 2003 at 10:36:30PM +0200, dominik.vogt_at_gmx.de 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 [_at_screen] geometry option. There may be better solutions
> > > but it seems to work. I hope that helps.
> >
> > But it already has support for '_at_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(+x+y_at_screen, Tile foo, ...)
> >
> > ?! What would that be good for?
>
> I'm not sure what you mean.
I was confused.
> I think there are two ways to specify the size and position of
> FvwmButtons:
>
> 1. *FvwmButtons: Geometry 272x68-0-0_at_p
> 2. *FvwmButtons: ButtonGeometry 68x68-0-0_at_p
>
> 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 '_at_screen' in these configuration
> options.
>
> Please correct me if I'm wrong.
I have fixed it in the parse_window_geometry() function.
Bye
Dominik ^_^ ^_^
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Apr 25 2003 - 02:56:20 BST