-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TitleStyle Active Colorset fg color apparently ignored #1048
Comments
I think the issue is that The fvwm3 internal defaults are
I don't know if this is a bug, the colorset settings created by There might be something to look into here, but this may require an overhaul on things work. |
To add to this, here is an expert from the manual page (though kinda hard to find): "Earlier versions allowed to use the HilightColorset and WindowFont commands in decors. This is no longer possible. Please use the Style command with the HilightColrset and Font options." I suspect this applies here too, The font and its foreground color of the active window must now be only set though the Style command. So it seems at least somewhat intentional that the font gets its color from the Style and not the Decor (TitleStyle). |
Thanks for that information! I'll try to test it out in the next couple days. |
I'll close this. @edanaher -- feel free to reopen if there's any other issues. |
Upfront Information
Please provide the following information by running the command and providing
the output.
fvwm3 --version
)NixOS unstable
uname -sp
)Linux unknown
Expected Behaviour
When using colorsets, the fg attribute should be used for the titlebar text in both active and inactive windows.
Actual Behaviour
It looks like the fg attribute on the colorset is ignored for active windows. A fairly minimal excerpt from my config, with tweaks to make the issue more obvious:
In this case, inactive windows have red title text, but the active window title text is black. Oddly, fvwm2 also had this issue; I added a workaround ages ago that I forgot about (commented out above). That no longer works in fvwm3, though changing the default colorset does fix the issue, but has other effects.
AFAICT, it's just active windows that are impacted, and changing the color set numbers doesn't seem to impact that bug. I suspect that whatever special handling fvwm2 had for the HilightFore may be related.
It's also entirely possible that this is how ColorSets are supposed to work; I've never fully understood them, but this seems like inconsistent behavior that inactive windows are affected by the fg color, but the active one isn't.
Steps to Reproduce
The config file provided above is pretty minimal, and behavior is similar but easier to work around in fvwm2.
The text was updated successfully, but these errors were encountered: