2009/10/6 Jamie Griffin <[email protected]>:
>> I've re-read the man page you suggested, however i'm still unclear exactly
>> how i do it. And if i was to try and use two instances of FvwmButtons, how
>> would i do that?
What is it with people replying off-list? I don't do FVWM
"""consultancy""". *Please* keep this on list.
You're asking me to basically give you the answer, but I really can't
be arsed. With a container, you basically have a separate FvwmButtons
instance inside FvwmButtons. So, your container would be the button
to give you the "L" shape -- that is, something like this:
| e |
| a | b | c |
(You'd to best to view that using a fixed-width font). Basically,
button "c" would be where you'd define your container for buttons "b",
and "a".
Or, you could just produce something like this:
DestroyModuleConfig Foo:*
*Foo: Columns 2
*Foo: Rows 2
*Foo: (1x1, ...)
*Foo: (1x1, ...)
FvwmButtons Foo -g some_location
... where that defines buttons "a" and "b" as a separate FvwmButtons
instance, slotted into place with a known geometry.
Or, you could also use a panel. Again, see "CREATING PANELS" section
in "man fvwmbuttons".
>
> In my current config file i have the following:
>
> *FvwmButtonsGeometry +928+20
That's wrong, even for FVWM 2.4.X -- module commands are now in the form:
*Alias: Option value
...note the colon.
> *FvwmButtons(Frame 2 Padding 0 0 Container(Columns
> 1 Frame 1 \
>
> Padding 0 0))
These options want separating with commas.
-- Thomas Adam
