The end of an era (designing a Latte-free alternative dr460nized setup)

This is a different widget, the one Dragonized currently uses causes blank space.

I was testing Active Window Control on kde-git and that space was left blank if not using standard white arrow buttons. It's possible I didn't use the right setting, though, which is why I will try again.

I am on 5.26.90. This is the setting for changing the look:

2 Likes

I think I could came up with something very very interesting.

For comparison, this is how squared the focus-hover is by default in Sweet (I did not change this):
1

Launcher-hover now with rounded corners, 50% opacity:
50-1
50-2

40% opacity:
40

30% opacity:
30

20% opacity:
20-1
20-2

My choices fall between 30 and 40%.
20% fades away too much.
50% is on the edge of looking like an icon by itself, which is not, yet again, the spirit of Sweet Theme.

I think 40% the color is more vivid than 30.

4 Likes

I think I prefer the 20%! It is more subtle, but still obvious what is highlighted and looks good I think.

I like the rounded corners, nice one!

3 Likes

Is this intended behaviour? (look at text) Dragonized Next, Plasma 5.26.90

@dr460nf1r3 do the Plasma native panels offer lower resource usage (since they are already loaded and part of framework) and better performance than Latte. I also run this on a much lower end laptop (yes I know I should be using Lite version but what can I say, I like KDE and all the utils, and its not that bad). I think it should, yes?

1 Like

If you are on very low end then yes, panels are lighter than Latte and it is worth the switch.

3 Likes

I added Active Window Control and enabled borderless maximized again

2 Likes

I can only guess probably not? That transparent text effect only seems to be present in some windows' text. I am seeing the same thing you are and I am not using Dragonized Next or the latest beta plasma (I'm using stable 5.26.5)

Then I think it is intended but used for a long time before Dragonized Next.

1 Like

The rounded corners are much better and I think either the 30 or 40% opacity. The the 50 seems a bit blury to me, and the 20% too solid.

EDIT:

@FGD TOO funny cause I just scrolled back up and finished reading your post. Specifically the bottom part of it that I didn't read before posting the above.

1 Like

Talking about Active Window Control, I've noticed a potential bug that seems to only be present when the window buttons are showing (either with its on all the time setting or only when maximized). It seems the bug has to do with an interaction with Steam's menus (at least Native stable). After clicking around and hovering around its menu (with the large STORE LIBRARY etc menu), it seems to crash plasma (but it will reload automatically).
Looking at the journal, it gives me a message about (libQt5Core.so.5 + 0x2d8b2c) every time it happens. I can only assume its because it actively tries to refresh information quickly (hovering over the menus gives a window title of Plasma Desktop instead of its usual Steam title).
I am not totally sure if this plasma crashing bug is just with my specifically customized plasma panel or not, and I will try more extensive testing on a guest account with just the buttons from Active Window Control later if needed.

(libQt5Core.so.5 + 0x2d8b2c)
                                                 #4  0x00007f27e66865ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2865ac)
                                                 #5  0x00007f27e64e725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f)
                                                 #6  0x00007f27e78f0cba n/a (libQt5DBus.so.5 + 0x23cba)
                                                 #7  0x00007f27e64e432a n/a (libQt5Core.so.5 + 0xe432a)
                                                 #8  0x00007f27e5e9f8fd n/a (libc.so.6 + 0x868fd)
                                                 #9  0x00007f27e5f21d20 n/a (libc.so.6 + 0x108d20)
                                                 
                                                 Stack trace of thread 116569:
                                                 #0  0x00007f27e5f16cd1 pselect (libc.so.6 + 0xfdcd1)
                                                 #1  0x00007f27e4096524 n/a (libusbmuxd-2.0.so.6 + 0x2524)
                                                 #2  0x00007f27e40978a9 n/a (libusbmuxd-2.0.so.6 + 0x38a9)
                                                 #3  0x00007f27e5e9f8fd n/a (libc.so.6 + 0x868fd)
                                                 #4  0x00007f27e5f21d20 n/a (libc.so.6 + 0x108d20)
                                                 
                                                 Stack trace of thread 116589:
                                                 #0  0x00007f27e5e9c4b6 n/a (libc.so.6 + 0x834b6)
                                                 #1  0x00007f27e5e9ecd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
                                                 #2  0x00007f27e64eb7c4 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xeb7c4)
                                                 #3  0x00007f27e81fd393 n/a (libQt5Quick.so.5 + 0x1fd393)
                                                 #4  0x00007f27e64e432a n/a (libQt5Core.so.5 + 0xe432a)
                                                 #5  0x00007f27e5e9f8fd n/a (libc.so.6 + 0x868fd)
                                                 #6  0x00007f27e5f21d20 n/a (libc.so.6 + 0x108d20)
                                                 
                                                 Stack trace of thread 116577:
                                                 #0  0x00007f27e5f1437f __poll (libc.so.6 + 0xfb37f)
                                                 #1  0x00007f27e4cc4c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                                                 #2  0x00007f27e4c6c0e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                                                 #3  0x00007f27e66d8b2c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
1 Like

I configured AWC to show for maximized windows only and when I hover on Store Library etc. Plasma treats the context menu as a seperate window and focuses to it. When this happens AWC disappears because the so-called "window" is not maximized.

1 Like

Saw that you have it set that way.
Shouldn't be an issue unless there is a maximized Steam window then.

Never seen transparent txt like that, never heard. But so far I could not reproduce either. This is on bare metal machine or VM?
Could be something related to Kvantum settings.

I checked that during my testing and I believe it does offer lower resources usage. I will try to come up with numbers later this week.
Performance is faster and smoother for me. For example, it launches on login A LOT quicker than Latte. Interaction with the dock and panel is virtually instant too.

3 Likes

That's... odd. I've noticed it for a very long time. It only seems to be a specific kind of window text however. You did try looking at the same window in Active Window Control, right? Otherwise it might be a specific graphics related bug... hmm...

Not recently, only 22-23 days ago. It's on my list to go back and retry, though, but at that time there weren't any txt issue in AWC, neither other applets' menu (inline battery, systray, weather, etc.).

1 Like

Dr460nized co-maintainer

It has happened :grin:

5 Likes

If you guys are are stilling figuring out the design - I'd like the Dock to have "hover Zoom icons". This gives me less static, more intuitive feel over the dock (I use 5% zoom on hover).