-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
FvwmPager: WindowFore black seems to be broken #1105
Comments
I am unable to reproduce this using the config you provided, though I do notice an issue with |
The black pixel is 0, so if a user configures the window foreground or focus foreground to be black, when testing if the pixel has been configured, the test fails and the pager falls back to using the pixel provided by fvwm. Instead use ULONG_MAX to identify if the window foreground and focus foreground pixel has been defined by the user or not. This fixes #1105.
@harridu Try this branch, https://github.com/fvwmorg/fvwm3/tree/js/gh-1105, it seems to fix the issue I saw. |
Yup, problem seems to be gone with commit e1f12ad. Thank you very much |
Fvwm3 version (run:
fvwm3 --version
)fvwm3 1.1.1 (released)
with support for: ReadLine, XPM, PNG, Shape, XShm, SM, Bidi text, XRandR, XRender, XCursor, XFT, NLS
commit f789db3
Linux distribution or BSD name/version
Debian Sid
Linux cecil.afaics.de 6.11.7-raw SMP PREEMPT_DYNAMIC Fri Nov 8 19:02:08 CET 2024 x86_64 GNU/Linux
Actual Behaviour
Moving from version 1.1.0 to the top of the main branch (commit f789db3) the WindowFore option for FvwmPager appears to be broken. 1.1.0:
commit f789db3:
Please note the white frames, even though my FvwmPager config doesn't mention white at all:
If I set WindowFore to #010101, then the new fvwm3 works as 1.1.0.
I understand that I should use colorsets. This is WIP. However, this should not affect WindowFore.
The text was updated successfully, but these errors were encountered: