Skip to content

fix(wayland): render layer-shell window opacity - #38

Closed
inayayousfi wants to merge 1 commit into
mainfrom
fix/wayland-opacity
Closed

inayayousfi wants to merge 1 commit into
mainfrom
fix/wayland-opacity

Conversation

@inayayousfi

Copy link
Copy Markdown
Contributor

Written by inayayousfi, typed by gpt-5.6-sol running in OpenCode.
Every call here is inayayousfi's, and no agent acted on its own.

Summary

  • Apply opacity to the rendered widget tree for Wayland layer-shell windows, where native window opacity is unavailable.
  • Keep the layer-shell surface at full native opacity to avoid applying alpha twice.
  • Preserve the existing native opacity path for Windows and X11.

Architecture

RuntimeWindow adapts the existing Qt opacity operation at the window boundary. Runtime commands, input blocking, overlay backend selection, and window configuration remain unchanged.

Testing

  • .venv-windows/Scripts/python.exe -m flake8 --select=F,E9,W6 src
  • .venv-windows/Scripts/python.exe -m unittest discover -s tests (168 passed, 1 skipped)

Live visual validation on KDE Plasma layer-shell remains required because the WSL development environment cannot provide that compositor path.

Apply opacity to the rendered widget tree when Wayland layer-shell cannot provide native surface opacity. Keep native window opacity unchanged for Windows and X11.

Written by inayayousfi, typed by gpt-5.6-sol running in OpenCode.
Every call here is inayayousfi's, and no agent acted on its own.
@inayayousfi

Copy link
Copy Markdown
Contributor Author

Written by inayayousfi, typed by gpt-5.6-sol running in OpenCode.
Every call here is inayayousfi's, and no agent acted on its own.

Closing this because #39 supersedes it. PR #39 includes the Wayland content-opacity fix in a shared opacity controller, covers both layer-shell and KWin input-panel windows, and routes runtime opacity changes through that implementation.

@inayayousfi
inayayousfi deleted the fix/wayland-opacity branch August 25, 2026 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant