@Christoph-Hart
Working!
Thanks!

Thanks both!

@ustk in fact I can do it perfectly from the code but as I assigned about thirty buttons from the property interface, I didn't want to redo everything. I would have thought there would be a solution.
I just thought, what if I want to retrieve the value of the button but from the effect and not from the button c is possible?

yes I only want a single label, indeed it will display the last selected button but that does not pose a problem for me.
the solution to recover the value from the effect can be done

@Christoph-Hart Link is dead.

Its been some time now since my last post.. Someone must know...?
I can't figure it out...
Could some one please take a minute to have a look at the script?
Thanks

@D-Williams23 No problem!

About editing the C++ though. I've been learning it lately, is it worth going in there and trying to figure that out? Do you know which folder has that particular file?

You can find the file and the header file here: HISE/hi_components/plugin_components/PresetBrowserComponents.cpp

@Christoph-Hart If not too much of a pain, is there a possibility to open other files such as .cpp or .h in a ScriptEditor tab?
If the code editor improves, I could be cool not having to rely on third party editors anymore, just sayin'...

iiuc mdaLimiter.cpp swaps attack and release param indices, which probably needs to be reflected in MdaEffectWrapper.h

also, the desmos plots below show mappings from unity range to the synthesis range (equations taken from mdaLimiter.cpp). the release nonlinearity / black curve looks kind of suspicious to me. haven't analyzed the actual dsp algorithm though, so maybe it is just fine.

Link Preview Image Desmos | Graphing Calculator

Explore math with our beautiful, free online graphing calculator. Graph functions, plot points, visualize algebraic equations, add sliders, animate graphs, and more.

favicon

Desmos (www.desmos.com)

@ustk no ahah that’s why it was not working! Thanks a lot!

I've just updated the jucer template output by HISE to include the path to the SDK3 folder inside the JUCE directory by default when exporting a VST3 plugin. This will avoid users having to copy files over to the version inside the tools/SDK folder and you won't have to worry about adding the path to the jucer project manually.

I've also enabled bigobj by default on VS17 and improved the naming of some of the output binaries (doesn't make a different most of the time but stops me getting confused writing my exporter app trying to keep track of all the different variations of binary name)

@Christoph-Hart I've made a pull request to scriptnode for these changes, thanks.

@Dalart Will go with you idea for now ☺ ,
Thank you

@DanH Big thanks my friend... saved the day! That worked.

Ohhh I see... Thanks everyone 👍

@d-healey Oh I see, sorry... I've only seen the mouseCallback and not properly read the question :)

@Christoph-Hart It's not workin on arrays generated by FileSystem.

@Christoph-Hart Ok, so it won't cause any harm if I set it as default in my exporter app?

<3<3<3<3<3<3

include("arrayfile.js"); Console.print(fruit.Data[Math.randInt(0, 3)]);

@ustk Yep, it's due to my resolution, when I enlarge my gui it works. Thanks!