-
Notifications
You must be signed in to change notification settings - Fork 12
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
blur/rounded-corners: rewrite #68
Conversation
…regions that don't have rounded corners
I'm using Breeze with disabled titlebar. In your picture it looks like SierraBreezeEnhanced specifies its own blur region, which needs to be overridden by enabling Blur window decorations as well. The bottom corner appears to be rounded properly, but you'll need an effect that rounds the window as well, such as KDE-Rounded-Corners or LightlyShaders. |
@taj-ny what should be border radii in each of the components (LightlyShaders/SierraBreezeEnhanced/Lightly/Force Blur)? Should be all the same (ex. 8px)? I enabled all of them and I still experience artifacts, but only for window titlebar also Force blur together with LightlyShaders makes most apps blurry (see a-parhom/LightlyShaders#130) |
Go to force blur settings, enable Blur window decorations as well and keep adjusting the top corner radius until it looks fine. Applications becoming blurry when using LightlyShaders/KDE-Rounded-Corners with scaling is a KWin bug. |
@taj-ny should I file a bug to KDE? How do I reproduce it properly? I mean without involving desktop effects directly (like via c++ or smth idk) |
…ectangle's height
It has already been reported. The bug report is about the Colorblindness Correction effect, but it's the same bug that affects LightlyShaders/KDE-Rounded-Corners. |
I've fixed the low texture resolution issue when using scaling on Wayland, but sometimes its position is off by 1 pixel. A similar issue affects many effects, including Blur, Invert, Colorblindness Correction, LightlyShaders and KDE-Rounded-Corners. EDIT: The issue described above will not occur when antialiasing is set to 0. It's also interesting how even on 200% scaling the blur looks fine, even though the texture that's being blurred has a resolution that's two times smaller. |
…paque region when using fake blur
…que region when using fake blur
There are some minor issues with antialiasing when using scaling on Wayland but other than that everything seems to be working perfectly. I'll probably make a release tomorrow. Floating panels are now rounded correctly and non-floating panels aren't at all anymore. |
…asing is enabled" This reverts commit bb070a4.
…aximized/fullscreen
This is a rewrite of the rounded corners implementation, which has much better-looking corners. There's probably a better way to do it, but for now that's the simplest and most efficient way of doing it that I can implement myself.
The corner radiuses are also now decimal values.
Comparison
The pictures were made in the worst possible situation: maximum blur strength with the corner being on a darker surface right next to a bright one.
Blur only (15px radius)
Before
After
No antialiasing:
0,5 antialiasing:
With window-rounding effects (15px radius)
KDE-Rounded-Corners
17px blur radius with 1 antialiasing
Couldn't get it to match perfectly, but it's definitely better than before.
LightlyShaders
14,75px blur radius with 0,5 antialiasing
Looks perfect.
To do