On 15 Oct 1997, Kai Grossjohann wrote:
> >>>>> On Wed, 15 Oct 1997, Greg Fall said:
>
> Greg> I don't see how M4 can do any better for you than just
> Greg> hard-coding *FvwmButtonsGeometry in there. Sure, you can make
> Greg> some kind of BUTTONBARWIDTH macro, but that really makes it no
> Greg> easier. Anyway, thanks for your comments.
>
> SCREEN_WIDTH: predefined m4 macro
> FVWM_BUTTONS_WIDTH: define this macro yourself
> FVWM_BUTTONS_X := SCREEN_WIDTH/2 - FVWM_BUTTON_WIDTH/2
> let m4 compute this for you
>
> kai
Okay, that's fine. But would it be possible to write a method that
interferes at some point between FvwmButtons being assembled and
FvwmButtons being placed on the screen, at which time the window and
border width, as well as the screeen width, are figured out and the above
calculation happens, then FvwmButtons is given an appropriate geometry
spec? Doing it by hand, even if you use m4 to avoid a little arithmetic,
is a little unsatisfying.
--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
Greg Fall
gmfall_at_engin.umich.edu
http://www-personal.engin.umich.edu/~gmfall
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Wed Oct 15 1997 - 10:12:44 BST