Finally: Fully customize stock UI elements with a scripted LookAndFeel

[clumsybear]

@d-healey said in Finally: Fully customize stock UI elements with a scripted LookAndFeel:

@Dalart

Yeah I found it in scriptnode, now to find some tutorials or something to learn how to do this paint stuff.

https://www.patreon.com/davidhealey ;)

I can recommend @d-healey s paint routine videos :)

[ustk]

@Dalart In the doc you'll find examples

[d.healey]

Found a bug. I customized a combo box to have an invisible background but this has also affected the rendering of HISE's windows.

Also I have a usability question. What happens if I want to customize two controls of the same type but have them look different? Is it possible to attach the paint routine to individual controls or must be use a control statement within the paint routine to determine how each control should be painted?

[Christoph Hart]

Nope, it overrides the global look and feel. However you can use the colour properties to customize individual UI elements at least a little bit.

[d.healey]

Knobs/Sliders next please :D

[Lindon]

@d-healey said in Finally: Fully customize stock UI elements with a scripted LookAndFeel:

@ustk said in Finally: Fully customize stock UI elements with a scripted LookAndFeel:

• MidiLearnPanel => column widths

Side request - can you make the midi learn panel even more useful by adding the ability to select the assigned CC from a right click menu? This will be very helpful for users who don't have many hardware controllers but still want to use CC automation in their DAW/host.

Assuming this request didnt get executed? If so add my vote for it please.

[Christoph Hart]

There you go:

https://github.com/christophhart/HISE/commit/d30e21dd1fb7f10f037986200fef6ab3e293d4bc

[Lindon]

@Christoph-Hart said in Finally: Fully customize stock UI elements with a scripted LookAndFeel:

There you go:

https://github.com/christophhart/HISE/commit/d30e21dd1fb7f10f037986200fef6ab3e293d4bc

hey @d-healey - is this in your latest commit? If not any chance of adding it?

[d.healey]

I think at this point it really would be best if Christoph could merge my branch into the official repo.

[d.healey]

@Christoph-Hart Who else needs to sign the agreement thingy for you to merge? I can send dogs after them if needed :)

[ustk]

@d-healey We were 3, two of us did it :)
@Levitanus doesn't seem to be an active member for a while...
Maybe Christoph could reach him by email? traditional mail? carrier pigeon?

[d.healey]

@ustk He's active on VI-Control. I'll send him a message there.

[Levitanus]

Hi, I'm ready to sign. Ohhh. How complicated things are... It's just few lines from the JUCE repo)

[Levitanus]

Can't see what should I do

[d.healey]

@Levitanus I think you'll need to wait for Christoph to send you the doc tomorrow.

[Levitanus]

OK, thanks. pianoist@ya.ru for the case

[Christoph Hart]

Actually, if you just pasted some lines over from the JUCE library, you don't need to sign it (because then the JUCE guys have the copyright). I've just seen your name in the commit history and wanted to make sure that everything is cleared before merging.

Alrighty then, we're good to go. @d-healey can you send me the link to the branch I should merge? I kind of lost track :)

[d.healey]

@Christoph-Hart

https://github.com/davidhealey/HISE/tree/develop

There is a pull request open for it.

[Christoph Hart]

Alrighty, done :)

[d.healey]

Woohoo!!!!