[Suggestion] Improvements to the way colours are managed in Components

[daniel]

If you set a colour on the lookAndFeel, it will have an effect for all components using that LookAndFeel.

getLookAndFeel().setColour (Slider::thumbColourId, Colours::red);

will change all slider’s thumb to red, if they use that LookAndFeel.
If a Component doesn’t have it’s own LookAndFeel, it will use the parent’s one. So this kind of inheritance is already happening.
The colours you set directly on a Component is only used for that particular Component.

OT: I wanted designers to be able to create all the layout and colour schemes for my plugins, thats why I wrote this module, that lets you design your plugin, and it uses the CSS paradigm for colouring and other style effects (borders, captions, margins, etc.)

Visual plugin designer - PluginGuiMagic - now free (27.7.2023)

I wanted to share here my latest project. When developing, having a default ProcessorEditor is a great help. But once you go to the designing stage, it is always tedious, all the compiling, looking, recompiling… Also it’s good, if not a developer but a designer does the visual arts. But do we want designers to write C++? C++ is not the best language to write GUIs with. But it is a great language to write tools. So I wrote a design tool to design, layout, style and colourise a Plugin (and pote…

Maybe that is an alternative…