If you use the processorId property it doesnt have to call into a script function so there is a tiny performance overhead, but that should be neglible. Stick to the properties for simple connection out of convenience and use the script callback if you need a custom logic.

@d-healey I will think about it ,
thank you for your help

@ustk That looks rather solid as well tbh! 🤔

@Glyn Have fun!

@Christoph-Hart that was fast - super - thank you

@MikeB https://github.com/christophhart/HISE/commits/scriptnode_codegen_rewrite.atom

@BWSounds Possibly an issue with a script that controls those buttons?

@Christoph-Hart said in Suddenly hitting snex errors when compiling... - SOLVED:

Yes, please try again, they should be fixed now.

Yep... It's a Christmas tree compile with about 389 shiny warning signs, but it's a successful build nonetheless... 🎄🙏🥳💪

Now I only need to find a way to open my project with it. Because it crashes every time I try... I tried disabling modules, but that hasn't helped so far...

BTW, I discovered the OpenGL Driver Monitor and the Open GL Profiler yesterday in Additional Tools for Xcode... Would that be of any help to root out my OpenGL probs?!

EDIT:

Not sure if this helps. That is what is crashing my plugin that I am trying to open in codegen_rewrite... I managed to open it by now by disabling all modules... but as soon as I boot them back up it crashes... Maybe it would be a good idea for me to disable OpenGL altogether for now?

Screenshot 2021-06-16 at 10.27.57.png

@Christoph-Hart Oh, I see it was for graphics... On my side, it was for creating random oscillators that are not just a crazy random function but something more controlled...

@Lindon
@d-healey

Ok - convinced 👍 👍 👍 👍 👍

That is even shorter
I still have a lot to learn.
Thank you very much - now I can finally sleep again,
after watching all of David's videos again the last few nights.

As I said, I think more visually than auditorily.
A picture tells me more than 100 words.

I will now analyse this for the time being and
see where my mistake was.

Once again many thanks to both of you

@d-healey If we can't do it dynamically with Content.setPropertiesFromJSON, then you can always put a panel over it (Save Preset) and play with "visible" true/false to hide the panel. It's a bit sketchy. But it's an idea.

@orange Oh right, I get it now, that's what confused me! Thanks :)

It looks interesting, although I don't think I'm a candidate I'm still very new 😅

@d-healey I ended up finding a previous version I backed up that wasn't too far off from where I was. It's a pain in the ass to have to redo but I'm going to bite the bullet and do it. If it happens again, I'll send it over.

Thanks again 💪

@Lindon yes that is one way to do it, but I want it to be as user-friendly as possible, so if it is possible to save it as a jpg, png or likewise?

Along with the Compiled binary send all @d-healey David Healey's Tutorials. This will be an extra push towards rapid learning.

@Lindon said in Maybe someone can help me here:

@MikeB - repeating your problem in multiple posts is just adding noise to teh forum.

An act of desperation 😁

@MikeB oh sorry, my bad! You mean overwriting the file manually? Then you're right… but is it not the case of almost all plugins? You can provide factory presets as a download in the user account to prevent losing them…
I don't know if it is possible to embed them in the plugin itself …

@yall Why not try it and see?

Put the flag HISE_USE_OPENGL_FOR_PLUGIN=1 in the usual places and set "GraphicRendering": true in CustomSettings to be able to switch in and out of OpenGL in your compiled plugin.