Skip to content
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: Use ULONG_MAX to identify a non configured Pixel. #1106

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

somiaj
Copy link
Collaborator

@somiaj somiaj commented Nov 10, 2024

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.

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.
@ThomasAdam ThomasAdam added type:bug Something's broken! relates:module Issue is in module code labels Nov 11, 2024
@ThomasAdam ThomasAdam added this to the 1.1.1 milestone Nov 11, 2024
@ThomasAdam ThomasAdam merged commit 3e0d960 into main Nov 11, 2024
12 checks passed
@ThomasAdam ThomasAdam deleted the js/gh-1105 branch November 11, 2024 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relates:module Issue is in module code type:bug Something's broken!
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

FvwmPager: WindowFore black seems to be broken
2 participants