(Easy way of) Unloading a plugin

[MortenMacFly]

Dear devs,

while developing my plugin for C::B a question came into my mind: After re-compiling the plugin that's being developed I normally shutdown C::B, copy the newly compiled plugin into the plugin folder and start C::B again to have it enabled. Here is the question: Is there an easier way to do this, i.e. have C::B at runtime to unload a plugin and/or reload it? It may be not possible at all (if I think about menu entries and stuff...) but maybe it is...?!

Morten.

[mandrav]

The code is there, but it is not used because we 've had several problems when loading/unloading on the fly, especially with plugins that add/remove menus etc.

After re-compiling the plugin that's being developed I normally shutdown C::B, copy the newly compiled plugin into the plugin folder and start C::B again to have it enabled.

You do know that you can run a second copy of C::B, don't you?

[MortenMacFly]

The code is there, but it is not used because we 've had several problems when loading/unloading on the fly, especially with plugins that add/remove menus etc.

Ah, I see... I can truely imagine the difficulties to implement the unloading if I see what one can do with the (fantastic) SDK... ;-)

You do know that you can run a second copy of C::B, don't you?

I know, but I've set C::B explicitely to run only a single instance. This ensures that if I click on a source file in the Explorer it's being opened in the (one) instance of C::B - which I prefer. (...and I would have to restart the copy as well...)

But I can live very well with the way I do it, it just could have been that there is a better way.

Thanks anyway, Morten.