Robin Schmidt
Robin Schmidt
well, ok - if you create modules at runtime then obviously some kind of editor must trigger the creation of the module. nothing wrong with that. what is the "e"...
soo...the oddness is actually not so much in creating AudioModules in the editor - but in creating AudioModules in the *constructor* of the editor
in this case, maybe what you want is a factory function? that is just some function that creates an object (typically via "new"), possibly calls some setup functions to initialize...
maybe look at my class AudioModuleFactory in the ToolChain.h/cpp file
how - if not via new - would you create the object?
> Do you want me to send out Toolchain to my 600 subscriber e-mail list? > Edit: I mean send a link to your website along with description? sure, why...
somehow, i actually like the grayscale gui. using scope for a product picture looks also good - but there could be some more action on the screen (higher glow, maybe)...
...i'm currently working on a hidden feature to take easy screenshots of editors (ctrl+alt+click will save a screenshot). that will make it convenient to create product pictures. no need to...
so, how do you get rid of the plugin window? i guess, it's possible to write a script for that for an image editor?
what has this to do with standalone vs plugin? has a standalone version different permissions than the plugins? i just added a standalone build version for ToolChain. seems to work...