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: WindowFore black seems to be broken #1105

Closed
harridu opened this issue Nov 10, 2024 · 3 comments · Fixed by #1106
Closed

FvwmPager: WindowFore black seems to be broken #1105

harridu opened this issue Nov 10, 2024 · 3 comments · Fixed by #1106
Labels
skip:changelog Issue/PR should skip CHANGELOG type:bug Something's broken!

Comments

@harridu
Copy link

harridu commented Nov 10, 2024

  • 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:

snapshot hfR7cm

commit f789db3:

snapshot 9Sr3Qz

Please note the white frames, even though my FvwmPager config doesn't mention white at all:

Style   "FvwmPager"             NoTitle, BorderWidth 0, HandleWidth 0, WindowListSkip, Sticky, StaysOnBottom

*FvwmPager: Fore black
*FvwmPager: Back black
*FvwmPager: HiFore black
*FvwmPager: HiBack gray10
#*FvwmPagerWindowColors black #404040 black #c06000
*FvwmPager: WindowBack #404040
*FvwmPager: WindowFore #000000
*FvwmPager: FocusBack #c06000
*FvwmPager: FocusFore black

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.

@harridu harridu added the type:bug Something's broken! label Nov 10, 2024
@ThomasAdam ThomasAdam added the skip:changelog Issue/PR should skip CHANGELOG label Nov 10, 2024
@ThomasAdam ThomasAdam added this to FVWM3 Nov 10, 2024
@github-project-automation github-project-automation bot moved this to To do in FVWM3 Nov 10, 2024
@somiaj
Copy link
Collaborator

somiaj commented Nov 10, 2024

I am unable to reproduce this using the config you provided, though I do notice an issue with FocusFore, which I think is related. I think the issue is I test if the fg pixel exists, otherwise fall back to the provided pixel of the window, and if the color is black, the pixel is actually 0, failing the test. Give me a moment.

somiaj added a commit that referenced this issue 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.
@somiaj
Copy link
Collaborator

somiaj commented Nov 10, 2024

@harridu Try this branch, https://github.com/fvwmorg/fvwm3/tree/js/gh-1105, it seems to fix the issue I saw.

@harridu
Copy link
Author

harridu commented Nov 10, 2024

Yup, problem seems to be gone with commit e1f12ad.

Thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip:changelog Issue/PR should skip CHANGELOG type:bug Something's broken!
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants