@hisefilo Yes, that sounds cool .

@Alex-Paradis you install each expansion folder in the plugin configurations' folder (in appData) as it was in the Hise Project. Yes. I think you can put the samples somewhere else though and add a LinkWindows file to the expansions folder to point to the correct location, just like with your normal HISE project. This would need to be done by the installer and might screw things up for the user if they move the samples at a later date. It would be good if the relocate samples button in HISE showed the location for the currently loaded expansion - I might have a look at the source and see if there is anything I can do there, if not we can just continue to nag Christoph Will the expansions still work If I create an new updated version of my instrument? As long as there a way to list them all in the app and that they work as they were before. Yes Where do I put the expansions in Mac? I assume they go in the Mac configurations folder where your other HISE project's files are put on first run. /Library if I remember correctly.

Ah, ok, this makes sense now! Thanks again!

@TNTHM

Thanks, good to know I made a workaround so it's all good.

@d-healey Nop. Only on windows. I will try on my MacBook now

@ustk thanx

@TNTHM A simple google search gave me this link: https://docs.monaca.io/en/products_guide/monaca_ide/deploy/non_market_deploy/ It seems to be rather easy, but I never tried myself (still don't have an apple dev account anyway...) Tell me if it helps

@d-healey You rock Now we have a new dev, there will be no time between Hise 3 and Hise 4...

@lalalandsynth Ok I see thanks

@ustk Yep , saw it ..:) Now it compiles but no pic shown , lol ....getting there . what do you mean by update the image pool ? I am assuming I can place it in the images folder and show it via that script ? EDIT: It works !

Dave is right, every UI control has to be declared at the beginning. The reason for this is that the UI controls also act as data model and for the sake of preset consistency you need to have every slot defined (see https://docs.hise.audio/working-with-hise/project-management/user-presets/index.html) With C++ you can easily decouple this connection and build up a separate data model which the UI controls act upon (which is what I am doing in PercX).

@lalalandsynth Not stupid, not obvious solution either

@ustk That's why I'm waiting so much for slider lookAndFeel function. If I modify all my parameters now I will have to do it again knowing that my plugin is 98% done... With this slider LAF, no more panel will be needed! That would be a killer...

@d-healey

@Christoph-Hart said in GetAllComponents: in fact it's so easy that David could do it himself Turns out you were correct! I've done it. I'll try doing it for effects and script processors too then I'll make a pull request! Update: I've added a getAllEffects function. I don't think I'll bother with one for script processors as the simple solution I posted above works just fine. I've created pull requests but if you want the changes sooner they are available in the getAllFunctions branch of my fork.

@ulrik thank you so much... highly aprecciated!

@Natanr I use Blender for all the 3d , then normally do an orthographic shot from Blender into Photoshop for the GUI version.

@Christoph-Hart Never mind, I figured it out, thanks!