-
Notifications
You must be signed in to change notification settings - Fork 39
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
Titlebar is always dimmed on Qt5 Wayland #125
Comments
cc: @polter-rnd |
Looks like it's because 6a3e8ff was aimed on Fedora-patched Qt and works incorrectly on vanilla 5.15.2 (which did not have that problem with titlebar dimming originally), sorry. I will look in detail later, will try to fix for both |
polter-rnd
added a commit
to polter-rnd/QGnomePlatform
that referenced
this issue
Dec 28, 2022
Don't use `window()->windowStates()` for checking active window state on vanilla Qt5, this works only on Qt6 or with KDE's patchset for Qt5. Fixes FedoraQt#125 Signed-off-by: Pavel Artsishevsky <[email protected]>
grulja
pushed a commit
that referenced
this issue
Jan 2, 2023
Don't use `window()->windowStates()` for checking active window state on vanilla Qt5, this works only on Qt6 or with KDE's patchset for Qt5. Fixes #125 Signed-off-by: Pavel Artsishevsky <[email protected]> Signed-off-by: Pavel Artsishevsky <[email protected]>
grulja
pushed a commit
that referenced
this issue
Mar 7, 2023
Don't use `window()->windowStates()` for checking active window state on vanilla Qt5, this works only on Qt6 or with KDE's patchset for Qt5. Fixes #125 Signed-off-by: Pavel Artsishevsky <[email protected]> Signed-off-by: Pavel Artsishevsky <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if this is a known issue, but here we are.
Because of 6a3e8ff, Qt5 applications running on Wayland will always have their titlebar in an inactive/unfocused state. Reverting this commit seems to restore the correct behavior.
Environment:
The text was updated successfully, but these errors were encountered: