Hello. I’ve been using fvwm2 2.6.9 until now. I’m trying to update to fvwm3 1.1.1 but I can’t set the color scheme properly.
Under fvwm2 I used the following:
Style * HilightFore black, HilightBack palevioletred
Style * Color lightgrey/dimgrey
Now, with fvwm3 I’ve set colorset like the following:
Colorset 0 Fore lightgrey, Back dimgrey
Colorset 1 Fore black, Back palevioletred
Style * Colorset 0
Style * HilightColorset 1
this worked fine for windows, but FvwmPager doesn’t look how I intended to.
With fvwm2, all windows in the pager had black borders. Active windows had palevioletred bg with black text, and inactive windows had dimgrey bg with lightgrey text.
Now, inactive windows’ border on pager is lightgrey like texts. How can I make all borders in the pager be black?
Thanks.
You can configure FvwmPager individually, read the FvwmPager manual page. Configuring FvwmPager will make it so you can configure exactly what it uses for the colors.
If you don’t configure the pager, it uses a combination of default colors and what the colors the windows in fvwm are. Looking at your pictures, it appears that the difference is in fvwm3 the pager now uses the foreground color of the window for both the text and the window border, while fvwm3 only used the foreground color for the text. I don’t recall if I meant to change this behavior when I updated the pager, but since you can just configure the pager to use the colors you want, I suggest you do that.
Looking closer, it appears that currently the pager doesn’t let you control the border color independently of the text color. The foreground color is used for both the border and text colors by the current pager. So you’ll have to setup the pager to use the same color for both (I admit that I don’t usually use labels so this wasn’t something I tested that much when updating things)
Looks like the logic in fvwm2’s pager was different on this front, and it didn’t update the border between the focused and unfocused windows. I’m unsure on if I should try to change this or not. I think the proper fix is to allow configuring the border color independently of the text color in the pager.
I see. It’s a bit unfortunate but it’s just a minor cosmetic difference, I guess I can live with it.
I also just noticed while comparing my screenshots that the border(?) (down & right) on FvwmPager differs between v2 and v3. I don’t care much about this one though…
Thanks for the response.
EDIT: with the fvwm3 config as in OP, my root menu uses fore lightgrey & back dimgrey. This behavior is different from fvwm2 where the root menu was using fore black and back grey(?) like when I load a blank config file.
Changing it like this solves it, but I’m not sure why. Does the Colorset number matter?
Yes the colorset matters. I guess I wasn’t clear, FvwmPager uses the foreground color for both the border of the mini window and the label (any text in the mini window) and the background color for the color of the mini window. You cannot have the border and and text be different colors (like the fvwm2 screen shot you had, but that was only a side affect of the windows using the foreground color of active windows for the border of both active and inactive windows).
So what I meant by you cannot get the same thing is I meant you cannot have the border color be black and the text color of the window be white. But you can have the border and text color both be black, in that case do what you did and configure the colorsets to give the foreground and background color you want. If you just want to make the foreground color of the windows black you could just do something like *FvwmPager: Fore black and that would make the border and text black of the inactive windows.
I guess I wasn’t being clear. I understood what you meant about fvwmpager.
What I meant after “EDIT:” was that having
Colorset 1 Fore lightgrey, Back dimgrey
Colorset 2 Fore black, Back palevioletred
Style * Colorset 1
Style * HilightColorset 2
produces my expected behavior while having
Colorset 0 Fore lightgrey, Back dimgrey
Colorset 1 Fore black, Back palevioletred
Style * Colorset 0
Style * HilightColorset 1
does not, (Root menu color changes) so i was curious if the Colorset number matters.
From Colorsets I do see these
######
# 3: Colorsets
#
# 0 - Default
# 1 - Inactive Windows
# 2 - Active Window
# 3 - Inactive Windows Borders
# 4 - Active Windows Borders
# 5 - Menu - Inactive Item
# 6 - Menu - Active Item
# 7 - Menu - Grayed Item
# 8 - Menu - Title
# 10+ Modules
###########
but there’s also this which is kinda confusing.
One can use any numbering convention for the Colorsets that fits your configs deisgn. If you don’t want to create one of your own, here is the one used in the default config.
Colorset 0 is the default colorset which will be used by other things if you change it. So if you change the default colorset you will change what menus look like. If you weren’t using the default colorset for the menu, it wouldn’t have changed unless you change the colorsets you configured the menus to use using MenuStyle.
Note the only colorsets that are defined by default are:
# Default colorsets to ensure they are set.
Colorset 0 fg black, bg grey
Colorset 1 fg black, bg grey25
Style * Colorset 1, HilightColorset 0
And outside of active windows using colorset 1 by default, anything else that uses a default colorset will always use 0. So that is why changing colorset 0 changed your menus. Though check out the default-config, it gives a lot more things that are configured and it follows the convention you listed. In that case since the menu’s don’t use colorset 0, changing colorset 0 won’t affect them.
