Expansions and executable HiseScript in AdditionalSourceCode folder

[David Healey]

@Lindon Can't you use the built-in preset browser?

I added expansion management controls to the expansion column recently.

[Lindon]

@David-Healey not what they want, they want it to look at least familiar for Kontakt Player users...so it has to be available at all times.

[David Healey]

@Lindon This could be. You could just have a single column off to the side

[Christoph Hart]

@Lindon I‘m pretty sure you can load another full instrument expansion without going back to the vanilla state, and a common shared left tab is not the hardest thing to implement - just make sure that code is self contained then ship the script files to each instrument using the asset manager.

[David Healey]

@Christoph-Hart Yes you can call setCurrentExpansion to change it.

[Lindon]

@David-Healey said in Expansions and executable HiseScript in AdditionalSourceCode folder:

@Lindon This could be. You could just have a single column off to the side

nope I mean this:

cant see how I can get the std preset browser to do this open/close - list instruments in a library approach, as well as all the single and dbl click functionality they want as well as search....

If you can see how to do it please let me know.

[Lindon]

@Christoph-Hart said in Expansions and executable HiseScript in AdditionalSourceCode folder:

@Lindon I‘m pretty sure you can load another full instrument expansion without going back to the vanilla state, and a common shared left tab is not the hardest thing to implement - just make sure that code is self contained then ship the script files to each instrument using the asset manager.

Yes this is my current plan...just sad I have to do it at all...

[David Healey]

@Lindon said in Expansions and executable HiseScript in AdditionalSourceCode folder:

just sad I have to do it at all.

It's very little extra work to include it in each project - if you use the new asset manager or the global script folder it's just a single line of code added to each project.

And charge accordingly :D

[Lindon]

@David-Healey said in Expansions and executable HiseScript in AdditionalSourceCode folder:

@Lindon said in Expansions and executable HiseScript in AdditionalSourceCode folder:

just sad I have to do it at all.

It's very little extra work to include it in each project - if you use the new asset manager or the global script folder it's just a single line of code added to each project.

And charge accordingly :D

..and as soon as the modulator bug is fixed and I can get on the latest release, then I can start to use this approach, until then...........

[David Healey]

@Lindon said in Expansions and executable HiseScript in AdditionalSourceCode folder:

until then...........

Global script folder

[Lindon]

@David-Healey said in Expansions and executable HiseScript in AdditionalSourceCode folder:

@Lindon said in Expansions and executable HiseScript in AdditionalSourceCode folder:

until then...........

Global script folder

yes....