Look and Feel - Toggle Buttons and the MIDI Sources panel...

[d.healey]

@Rudra-Ghosh Thanks for the example, that makes it more clear. I think I'm still going to avoid LAF for now, it feels too janky.

[ustk]

@d-healey The only thing I'm not confident is the Content.createPath() issue that makes the components disappearing as we mentioned in the related thread. I'm pretty confident about the rest. It is just that switching from custom to standard LAF makes some weirdness inside Hise (hence the reset function), but once compiled, everything works as it should.

[Lindon]

@d-healey said in Look and Feel - Toggle Buttons and the MIDI Sources panel...:

@Rudra-Ghosh Thanks for the example, that makes it more clear. I think I'm still going to avoid LAF for now, it feels too janky.

exactly what I decided......

[d.healey]

This post is deleted!

[ulrik]

@ustk I had to put

Content.createPath()

outside the function to get LAF to work with sliders, then it's working fine also when compiled

[ustk]

@ulrik yeah that might do it, but since Christoph said it was bad to refer to external variables in a custom LAF, I’m a bit confused on doing this...

[d.healey]

@ustk said in Look and Feel - Toggle Buttons and the MIDI Sources panel...:

@ulrik yeah that might do it, but since Christoph said it was bad to refer to external variables in a custom LAF, I’m a bit confused on doing this...

I'm a bit confused by it too. Christoph said

the methods that you give the LAF object must never access script variables outside their scope

But does that mean passing variables in as parameters or referring to variables within the function? What about external constants, won't they be resolved at compile time?

[d.healey]

Right, I've spent most of the day playing around with LAF. It's usable, but it takes some getting used to and it still feels janky.

[ustk]

But does that mean passing variables in as parameters or referring to variables within the function? What about external constants, won't they be resolved at compile time?

That was a question I asked Christoph but I can’t find the thread... my question was about colours, for instance, is it safe when you use your own external colour var inside a LAF

[d.healey]

@Christoph-Hart Any idea why paths are causing LAF controls to vanish?

[Christoph Hart]

Do you have a reproducible example?

[d.healey]

@Christoph-Hart I will in a minute little while, dinner's ready :D

[d.healey]

@Christoph-Hart said in Look and Feel - Toggle Buttons and the MIDI Sources panel...:

Do you have a reproducible example?

Actually @ustk has already provided an example - https://forum.hise.audio/topic/3732/custom-look-and-feel-component-id/12

[d.healey]

@ustk said in Look and Feel - Toggle Buttons and the MIDI Sources panel...:

@Lindon It's not yet merged, but if you can't wait, just remove or comment out this line:

Have you made a pull request?

[ustk]

@d-healey hum… dunno… I'll try to get my head around this tomorrow but pretty busy atm

[d.healey]

@ustk If it's just the one line I can do it on my fork and make a pull request, I just wanted to check first that you hadn't already made a pull request for it.

[ustk]

@d-healey I don't know if this line is enough, and I don't think I've pushed it so feel free to do it ;)

[d.healey]

I don't like fighting with the MIDI sources list LAF so I wrapped the functions in the scripting API instead so we are no longer tied to the floating tile.

It doesn't update the floating tile until I press the UI refresh button, but the idea is you'll use the API instead of the floating tile so it shouldn't be a problem in practice. I might wrap some more of these settings API functions too...