At some point we have to address that problem, I notice more and more posts just pasting the rubbish GPT output which dilutes the prestine information set available here in the forum.

Regarding the problem at hand, a single look at one of the many snippets / code examples from a good source should solve that problem, tuck inline before the function definition and pass it into the call.

@jpbc I think you're just missing a closing parenthesis and semi colon after the laf function registration.

By the way, you should probably use local look and feel here rather than global - it wasn't available when I made the video you're following.

@voxuer1 That means the thing on the left side of the dot doesn't have a function with that name. You probably need to get the reference to your module in a different way.

@d-healey
Thanks to you. I have not tried that. But now I have found the font. :-)

@d-healey Beautiful, thanks!

@d-healey Thank you!
I'll watch this in a bit.

@CyberGen Well, just by messing around, discovered that you can put the numbers instead of the builder.ChainIndexes.... So it's zero based:

builder.create("GlobalStaticTimeVariantModulator", "Attack Time Mod", ampEnvelope, 0); // for Attack Time, 1 for Attack Level, etc.

😁

@Simon Nope, only component values for components that are set to saveInPreset are.

@griffinboy you should set your fictional voice count, assign ids to array indexes and remove them when releasing notes. Then you can check along the array to fill the first empty index with a new od and set event data based on the index.

Your event data for individual voices is in another array, obviously, all ordered by voice order.

@d-healey It no longer crashes HISE :)

I'm using Encrypted expansions

@VirtualVirgin You could try table mode. You might also try using multiple viewports with lists - a bit like how the preset browser is laid out.

@d-healey Ah of course, that works, cheers David!

@Oli-Ullmann obj.text

@hujackus awesome!

bada-bump is there any update on this, didnt find any related commit and messing with it in hise beared no luck, dont know if I missed something or if its still in the works?

@Casmat Nope, you just have to match the shadow colour to the background. Experiment though you might get better results using radial gradients for example.

For more complicated functions you could pass an array of parameters and branch to different functions based on the length of the array.

For example

inline function myFunc(params: Array) { switch (params.length) { case 0: return subFunc0(); case 1: return subFunc1(params[0]); case 2: return subFunc2(params[0], params[1]); case 3: return subFunc3(params[0], params[1], params[2]); } }

@Lindon of course it is, thankyou.
I think I tried that with intensity and had to do it the way I posted for it to work so I just went straight to that for inverting.
Need to stop asking questions at 11pm when I’ve been going since dawn.
Thanks