This is in relation to the BoxSize attribute of FvwmButtons. The default is dumb which means that the overall size of the FvwmButtons instance stays the same, and as more buttons are created inside it, these buttons will grow and shrink to accommodate all of them.
With ButtonGeometry you can define both the location of FvwmButtons instance, and size of a “button” inside that instance.
So, FvwmButtons: ButtonGeometry 80x80-0+0 FvwmButtons: (3x2, Swallow “FvwmDada” “Module FvwmDada”)
Would make a 380 x 280 sized button, with FvwmDada inside.
Also the FvwmButtons instance would be located at the right upper corner on your screen (-0+0).
Actually, everything said to you is in the FvwmButtons man page. It just might not be very clear to yourself what the overall intention is, that’s all. It’s one of the side-effects of writing documentation to appeal to the masses. Invariably there’ll be a small minority who drown in syntax.
I did laugh at your suggestion. Yes, the man pages are checked. Yes, they do on occasion contain mistakes. But not on this occasion. I know the man pages are cumbersome at times, but if you read it carefully, and try things out, then a lot of the time, it makes sense.
From what I can tell of your posts so far, I don’t think it’s the man pages that are at all at fault, but rather you are. FVWM is not easy, and as hard as you’re trying, it seems as though you’re drowning at the same time. You seem to be asking so many different questions before you have well and truely found the answer to the one you were originally looking for.
To date, there has been almost 100 messages posted from you to this forum. Great. Except, a lot of them really are trivial. They’re things you could have found out for yourself, if only you had tried it for yourself. That is, by trial and error, and more easily, by looking at other people’s configuration files. We have a huge section dedicated to them – and over the month’s, they’ve been quite useful to a lot of people.
By all means, keep trying. But your accusations are unfounded in this instance.
Heheh, I know how frustrating it can be sometimes (Just wait until you get to the shell-quoting stuff with PipeRead)
But after you start trying things out and get something to work and re-read the man-page, you may find yourself slapping yourself in the forehead shouting “doh!”.
Meaning the information usually is there, but it is in such, umm… “general” -level, that it can be hard to understand.
I think that because fvwm is “the programmers windowmanager”, the prerequisites for user knowledge and manualpages and such are a bit on higher level than… well, to be honest, they aren’t much different level than, say, zsh. But surely any *nix stuff is on different level than, say, MS Windows.
I think you’re talking about two separate issues…:
*FB: Geometry XxY+A-B
is akin to “Module FvwmButtons FB -geometry fooxfoo+foo-foo” – it just sets the size and location of the FvwmButtons on screen.
*FB: ButtonsGeometry XxY+A-B
As you said, is the same as “Geometry”, excepting that the geometry specifies a single instance of a button. But the dimensions for that button will be ever so slightly less than what one would normally calculate for it, given certain rendering issues with buttons in general. You have to be careful if you use both Geometry and ButtonsGeometry – it’s possible to do so of course, but you’ll find that Geometry will often take over any other setting beforehand.
Thomas, thanks for clearing that out. I have always used just the ButtonGeometry -option, and left out the Geometry option.
I had the assumption you could use one, but not the other at same time.
Although I feel it is simpler to use just ButtonGeometry option, as you can define it’s location with it, too.
Just to mention, I didn’t mean that as swallowing a bait
(looking at number of posts to date…)
PS. Just for the record, “dumb” is the default, not smart or fixed for boxsize in FvwmButtons, atleast according to my ‘man FvwmButtons’.