-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
GTK+-3: coco theme does not have round borders without compositor #98
Comments
I see that in my VM with 3.18 as well. |
You're right, i see that with gtk+-3.16 too. |
Yes, same here. Looks like it started in 3.16 as I don't see this issue with 3.14. |
Which m-n-d version are you using with gt+-3.14? |
Latest from git... |
It seems that Coco actually has rounded borders, but w/o compositing, a black rectangle is painted around the notification window. Because Coco's background is black too, we see it as if the borders are not rounded. If you switch to Nodoka or Slider, you'll see the rounded corners and the black rectangle around the window. |
So I thought it was happening only when the whole MATE is built with GTK+3... but it turned out it's not so. I've built the GTK+3 migration branch in GTK+2 environments with 3.16 and 3.18, and it still happens. The issue looks similar to mate-desktop/marco#163, maybe they're related. @lukefromdc: can you please take a look at both issues? Currently I have no idea how to fix them... |
A transparent window is not possible without compositing with whatever I know pseudotransparency using cairo drawing works in GTK3 because it I've never once seen transparency in notification themes work without Recall that in 1.9/1.10, most or all of the notification themes gave a totally On 5/21/2016 at 9:31 AM, "monsta" [email protected] wrote:
|
Coco theme does not have round borders without compositor.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30627214-gtk-3-coco-theme-does-not-have-round-borders-without-compositor?utm_campaign=plugin&utm_content=tracker%2F1172660&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1172660&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: