It’s working for me? Note that the colour of keydowncolour() is affected by mouseoverkeycolour(). keydowncolour() mixes with mouseoverkeycolour() through an alpha channel. If mouseoverkeycolour() doesn’t have an alpha channel, then keydowncolour() won’t appear to work. It’s not the most intuitive, but I just followed what JUCE does.
[quote=“t_grey, post:4, topic:2152”]
I’m also having trouble with keywidth(), but haven’t gotten to test enough to be sure… but
Touche. I see it not. Odd. I’ll take a look.
It is not currently accessible through an identchannel. FYI, each widget has a valueTreePropertyChanged() method that is called each time you pass data to its identchannel. You can see below that the keyboard widget only updates colours and layout (handleCommonUpdates() handles the layout stuff).
I can add the key width stuff. It’s not something I ever thought people would want to control in real time.
I can’t see many people would want to either… and yet here I am
I’ve been working on this concept effect that lets you pick colors and attributes of widgets in real time to preview and then generate a “theme” config file. The more I can add, the better! But if it’s any significant work, it’s definitely not an important request by any stretch.
Well, this “effect” is intended to generate skins for the project I’ve been working on… but a lot of it could easily apply and be incorporated into any project. It writes a config file with macros, just include the file and call any widgets called using the macros.
I don’t know that I’ve seen Iain’s example for this tho, is it included with the default build?