https://bugs.kde.org/show_bug.cgi?id=365994

--- Comment #6 from Mircea Kitsune <sonichedgehog_hyperblas...@yahoo.com> ---
(In reply to Martin Gräßlin from comment #5)

Sorry about that, I wasn't aware you are the maintainer of Aurorae. Definitely
taking your point as an official stance then.

The reason I consider this strange is that svg elements can already be
colorized, which is how my themes work. The colorization simply doesn't happen
when a window rule sets it, although it does work when the global color scheme
is changed. I assumed that was just the window rule forgetting to notify KWin
about the color in the same way the main color scheme does, but of course I
don't know the code and if there's more involved. Is there a fundamental
difference between how the two work, that's getting in the way of a fix?

If the purpose of Aurorae is letting artists create themes the way they like
however, I do think this should be considered; The themes I made and listed in
the description were intended precisely to work with color scheme, and let
people play around with system colors in any way KDE lets them. Per-application
color sets are something I looked into for this very reason, until the ability
to force colors with window rules was recently implemented... which I hoped
would offer a way to do things like the random titlebar colors seen in Windows
10, until I noticed this limitation once I tried.

I think it should also be kept in mind that to the end user who's using such
themes, the appearance window rule not working seems like a bug. My thoughts
when I noticed this were "it works with the Breeze theme, it works with Oxygen,
it only doesn't work with Aurorae... clearly there's a problem with it". To
someone who knows the code and initial purpose it might be different, but to my
untrained eye it's an incomplete new feature and among the lines of "when I
select both X and Y, Z stops working".

Hopefully this offers more insight on why I'm suggesting this. I'll leave the
report open personally, since I'm hoping a solution isn't entirely out the
window either and you might come back to it at some point... you know best
though.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to