-
Notifications
You must be signed in to change notification settings - Fork 498
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
Root window not redrawn #225
Comments
Probably not a compton issue: we put a window between the root window and the client windows (so we can e.g. easily move 'm all to another output if neccessary), and it appears that this is what's causing the issue. |
Sorry for the late reply, firstly.
|
No problem, thanks for the confirmation! As you can imagine avoiding putting an 'intermediate' Notion workspace window between the root window and the client windows would be tricky. I've briefly looked into setting the opacity of the 'intermediate' window to 0%, but it seems that also affects the client windows - so that doesn't seem like a useful approach. Another way might be to tag 'intermediate' windows with some X property and patch the compositor to recognize (and ignore/skip) those windows. Does that make any sense? Do you know of any compositor that does something like that? |
Sorry, apparently I misunderstood the problem because I didn't read the SourceForge bug report.
They are already "tagged" as |
I have a window manager that leaves the root window untouched (I think, it's Notion), and put a background picture on it with wmsetbg.
When I run compton, the root window is no longer redrawn, and just shows whatever was last drawn on that location - e.g. the windows from the previous workspace or a window that has since been resized or moved away.
This is quite possibly not a compton issue, but perhaps you can point me in the right direction. Who is responsible for redrawing the root window and when?
(this issue was reported to the notion bugtracker as https://sourceforge.net/p/notion/bugs/73/ )
The text was updated successfully, but these errors were encountered: