Each time you make changes to your code you will need to reinstatement the plugin. Simply reloading your Reaper sessions should be enough. And quicker than deleting and re-instantiating the plugin. Btw, once you have exported your plugin you only need to modify the associated .csd, in your case the one inside the plugin bundle. Cabbage 1 could load a .vst bundle, Cabbage 2 does have support for this yet, but will do soon.
Tell me about it. I’m stuck to using the text editor provided by the JUCE library. It’s nowhere near as smooth as the QT text editor widget. I believe the editor in Cabbage 2 is better, but it’s can’t compare to other text editor. My hands are more or less tied here. [quote=“Tim_Mortimer, post:8, topic:760”]
I have also had a few odd messages pop up on export like ‘you must specify a 4 letter file suffix etc etc’ … that seems to have no effect on the resultant output however (which i can at least now confirm, & not wonder if that is a hidden source of a problem i was experiencing …)
[/quote]
Sounds like you’re using the older version of Cabbage. Try out the latest beta for Cabbage 2.[quote=“Tim_Mortimer, post:8, topic:760”]
as an aside, i did just observe however, in Cabbage studio, the GUI keyboard works fine on the instrument itself, but the keyboard across the bottom of the screen seems to not be transmitting note offs (or my instrument isn’t processing them more likely …) not sure if that is something you wish to / care to examine …
[/quote]
Cabbage Studio was a proof of concept. It has been swallowed up by Cabbage 2. Each instrument you run is itself a plugin node in an underlying audio graph. [quote=“Tim_Mortimer, post:8, topic:760”]
the good news from my perspective however is that this now appears to be working in Reaper …
[/quote]
That’s good. Reaper is pretty solid. I know people are doing some very extraordinary things with it and Cabbage, so the are proving to be quite a good fit for each other.
Make as much noise as you like 
For what it’s worth, one of the next things for me to do is to build a small Cabbage lite interface that will work with any editor. Cabbage 1 could be used with any editor you liked so long as you coded the GUI yourself. Many people were happy with this arrangement and could use Sublime, Atom, WinXound or any other editor for that matter, to create their instruments. To be honest, I tended to use it this way myself, which is why the text editor in Cabbage 1 didn’t get much love!