@Taihongcraft that goes along with the exporter window being cheap on the issue reports…
Check you network (main outer container node) is set to allow compilation
But it might be something else, hard to say from far away!

Also, expand the section C++ Node Properties and verify or post here a screenshot

@christoph-hart Great!
1st minor thing -> double click on the header to expand the window doesn't work anymore (at least on mac)

@Matt_SF @DanH thanks, I pushed the issue...

@Christoph-Hart BTW, is it possible to set DSP table points directly from script without the need of using a dummy table in the interface?
I can live with it, though it could be less messy not to have it and only use data arrays...

@IsoWalle A thing to explore if you use sliders is that they are at the right default value when you export the plugin
But it could also be an internal DSP thingy in the initialisation of the comp itself...

@Casmat This is probably the job for a broadcaster with attachToComponentMouseEvents

@d-healey Don't know yet, I'll check ;)

A few more discoveries:
My Inno script contains mods to make the uninstaller look a bit better.
When I remove that part, it's not reputed as a virus anymore when downloading (but still dangerous) so I can force the download.
But when running the installer, the SmartScreen pops-up so I can't go further

@LeeC Nope, I haven't yet. The solution would obviously be scriptnode but that means I have to move my pre-existing modules in a dsp graph. In my actual case it's not too much of an issue because my FX is based essentially on filters.

The main problem I can't resolve for now is the use of a table. Modulating in scriptnode with any waveform is easy, but the implementation of a table that is controlled from the main script seems to be rather complex, for me at least. I haven't a clue...