Author Topic: (Easy way of) Unloading a plugin  (Read 3641 times)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9468
(Easy way of) Unloading a plugin
« on: November 09, 2005, 01:08:37 pm »
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.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: (Easy way of) Unloading a plugin
« Reply #1 on: November 09, 2005, 01:30:42 pm »
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.

Quote
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?
Be patient!
This bug will be fixed soon...

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9468
Re: (Easy way of) Unloading a plugin
« Reply #2 on: November 09, 2005, 02:08:56 pm »
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... ;-)

Quote
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.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ