LAF ScriptSlider?

[Christoph Hart]

@d-healey Merge.

[Natan]

@d-healey @Christoph-Hart so Is This Stable To Build?
https://github.com/christophhart/HISE/commits/scriptnode

The Top One, Is The Latest, Right?
71f75e5 <<< This?

[Christoph Hart]

Yes, that should be fine.

[A Former User]

This post is deleted!

[d.healey]

I'm convinced that LAF is the way to go now for a custom UI without images.

[A Former User]

@d-healey I was experimenting with Lottie graphics yesterday and was totally blown away by its looks and possibilities! I don’t get what LAF is exactly tbh. But it looks really nice too!

[d.healey]

@vewilya I haven't used rlottie much but what I have done with it has looked nice, very smooth animation.

[ustk]

@vewilya Be just careful with Lottie since all actions aren't rendered/compatible with Hise. So complex animations might not work, keep them simple.
Custom LAF is a way to redraw the components (sliders, comboboxes, etc...) with fully customizable graphics (shapes and colours). So you don't necessarily need to recreate the components from script panels for full customizations, the original ones can now give you almost anything you want...

[DanH]

@ustk We seem to lose the 'boxes' around the option buttons when using laf - anyone else come across this?

[ustk]

@DanH Unfortunately, when using custom LAF, Hise LAF isn't separated from plugins LAF. The recommendation is to write your custom LAF and then deactivate it (comment) when working on the project. Then reactivate (uncomment) before export.
I'd like this to be different like many of us, but Christoph said it would be a nightmare to modify if I translate well his words...

[DanH]

@ustk yes but the blank boxes carry over into the plugin itself - for example at the beginning of the whole process, when installing the samples, and when overwriting a preset...

I'm guessing we don't have any workarounds at the moment! :face_with_tears_of_joy:

Look at this monster lol

[d.healey]

@DanH Yes we have a workaround - LAF :p

Solutions have been posted in this thread - https://forum.hise.audio/topic/3228/look-and-feel-toggle-buttons-and-the-midi-sources-panel/14

Basically you have to style everything yourself.

[ustk]

@DanH When you use a custom LAF you have to redesign the whole component as it starts from blank...

[A Former User]

@ustk Thanks. I'll keep that in mind! So I guess as long as the animations show in my GUI they are working, right? Or would I discover non-compatible animations only on vst/au/standalone export? So much stuff to learn... 🤯

[ustk]

@vewilya yeah I guess if it works in the project you won't have issues…

[DanH]

@d-healey Yup get that, just doesn't seem to be anything for those boxes... Are they appearing in your project?

[d.healey]

@DanH Oh I see what you mean. I'm not using the settings tile so I hadn't noticed. You could paint a panel behind the settings tile.

[DanH]

@d-healey Oh I mean for the button boxes in general, like for the below.... I get a hover box, but normally there's a static grey box for these kind of options/buttons

[d.healey]

@DanH I think you need to customise the LAF for alert boxes.

[Lindon]

@DanH said in LAF ScriptSlider?:

@d-healey Oh I mean for the button boxes in general, like for the below.... I get a hover box, but normally there's a static grey box for these kind of options/buttons

This is why I think LAF isnt very nice. If you start to use it then you have to restyle every component that a plug uses - including all the ones you dont use in your interface.. so all the dialog boxes etc....