Aurorae toggle buttons (window decorations) do not show "pressed" status

Help
1

So I have the three buttons that are toggled on an aurorae developed theme: keep on all desktops, above all windows, and below all windows. When these buttons are active they default to the “active window” state instead of the “active pressed” state as expected. My buttons remain on the active status always and I cannot see if a window is meant to be above or below windows through my window decorations. How do I do one of two things:

Edit the aurorae qml files and reload the package so that the “pressed” status shows when I toggle one of the buttons.

Update to an aurorae version that has the “pressed” status functioning. The newest version has the same behavior.

Or even a third thing I haven’t thought of that someone already fixed. Honestly at this point I’m wondering if others have this behavior as well.

2

Does anyone have this behavior as well with aurorae theme toggle buttons? Any time I will a question about this the communities go completely silent so I have no idea if I’m the only one.

3

No, you are definitely not alone. I have wondered about the silence regarding this, as well. I consider button state to be pretty core functionality for a window decoration, so I was surprised that something that big slipped through the cracks with the Aurorae v2 release - unless it’s intentional, that Aurorae is no longer supposed to support button states? Or perhaps some part of the implementation changed, requiring something to be added or changed in the button SVG files?

I’ve also had an issue with every titlebar being messed up when maximised. I believe it relates to this:

> Please note that in the case of a window with translucent widgets, the center element will be stretched to the size of the complete window.

But it seems to stretch the titlebar to the full length of the window, regardless of any translucency. I created my Aurorae theme myself, it is fully opaque, and it still had this issue. It’s not immediately obvious what’s going on, since if you use an opaque window decoration, then the bulk of the titlebar will be obscured. Anyway, I had to make a hacky workaround, which looks really weird in Inkscape, but where everything now aligns correctly only after being stretched. But it obviously only works for my exact screen resolution, so I need to make a custom version each for my laptop and my phone running Plasma Mobile.

Update to an aurorae version that has the “pressed” status functioning. The newest version has the same behavior.

Well, one possible solution is to go back to the Aurorae v1 engine, as it hasn’t been removed, and I don’t believe they intend to remove the option, which is nice. Something else that’s nice is that it’s quite easy to do - simply:

  1. Find and edit ~/.config/kwinrc
  2. Find the line library=org.kde.kwin.aurorae.v2 and change it to org.kde.kwin.aurorae
  3. Save and then reload/reapply your window decoration.

It’s great to have that option, but it’s something I am personally wont to do, since I have actually seen pretty significant performance gains with Aurorae v2 - and props to the devs for that! I’d love it if they’ll weigh in on these issues with button states and the titlebar looking borked when maximized. Are they bugs to report, or working as intended? Are there any fixes that can be applied on the user-end, or the decoration-creator-end, besides switching back to Aurorae v1?

4

Where would the aurorae.v2 qml files be? I found the regular aurorae files and looked at the various button states and operators, but changing them did nothing. Did kwin manage to install it under the radar and it uses different files than the original version?

5

Okay I now see that v2 is programmed in C++ to make it more fluid. How would I go about editing those files or checking the operators to see where the toggle portion is failing?