[frameworks-plasma] [Bug 452348] Opaque plasmoidheading.svg not used even when assets are present

[Niccolò Venerandi]

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

--- Comment #6 from Niccolò Venerandi <nicc...@venerandi.com> ---
(In reply to doncbugs from comment #5)
> Hmmm, I suppose I saw this coming when the introduction of opaque (solid?)
> did not support all plasmoid backgrounds.

Wait, no, plasmoid backgrounds *do* become opaque (solid) when a window is
maximized (or, at least, they should). The issue is that whilst plasmoid
backgrounds are declared in just one place for all of them it's really easy to
change it just there. Whereas for PlasmoidHeading, I can only think of needing
some custom code for each applet that uses it. 

> Is it out of the question to
> design panels that properly support the different asset sets for Plasma 6
> now that we have an idea of how things might be customized?

You gotta ask Marco Martin on this one; I have no idea. He knows all of the API
much, much better than me.

> I don't understand these 2 ideas. The fallback is generally the default
> widgets/ items, so I can't see any harm in it. Not to mention, I'm pretty
> sure it's just copy and paste the default one to ship something.

What I meant is: we do not encourage third party themes to use custom svgs in
the solid/ folder; right now we only support the panel background as far as I
know. So I would say: for now, consider solid/ to be a folder *only meant* for
the panel background.

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