Skip to content

Conversation

@wmww
Copy link
Owner

@wmww wmww commented Dec 11, 2020

This fixes #38 with no known unwanted side-effects. mapped isn't supposed to be set for custom surfaces, but I dug through all the code that uses it without spotting anything that might cause a problem. This also adds a test for #38.

By opening this pull request, I agree for my modifications to be licensed under whatever licenses are indicated at the start of the files I modified

@wmww
Copy link
Owner Author

wmww commented Dec 11, 2020

Please check if this fixes your problem @wb9688. If it does I'll merge and make a release.

@wb9688
Copy link

wb9688 commented Dec 11, 2020

This indeed fixes the problem. Thanks!

@wmww wmww merged commit de9b676 into master Dec 11, 2020
@wmww
Copy link
Owner Author

wmww commented Dec 12, 2020

@wb9688 the fix has now been released in v0.5.2. It will make it's time to get into distros as these things do.

@wmww wmww mentioned this pull request Feb 27, 2023
@wmww wmww deleted the fix-38 branch February 27, 2023 19:13
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.

(not so) harmless "Couldn't map window as subsurface" warning

3 participants