Bug #15396 2009-03-17 13:28

patuti

Closing multiple instances of C::B may keep wrong config

I'm using Code::Blocks 8.02 MingW

Windows XP SP 2

When you've got multiple instances of C::B running and you set some plugin configuration like enabling or disabling a few and then you close this instance (where you've just modified plugin setup) and then you close the other instance, the next time you open C::B it kept the configuration from the last one closed.

It may lead to a incorrect interpretation that C::B is having a problem saving the plugins setup, but the problem is that it seems that C::B saves the plugin setup from the latest instance closed.

Steps to reproduce:

Run 2 C::B instances;

In the first instance:

*Plugins->Manage Plugins;

*Enable/Disable a few plugins;

Close the "Manage plugins" window;

Close the current C::B instance;

Close the other C::B instance;

Run C::B again;

Plugins->Manage Plugins;

Your plugin setup should now look like the latest C::B instance closed (and not the one that you modified).

This may not be a bug, just a bad use of C::B but it can lead to bad interpretation of what is happening, it may seem that C::B is buggy at first sight.

If the plugins setup could be saved by the time that you close the "Manage Plugins" window and do not overwrite it when you close the C::B instance apparently it would solve the issue.

Category

Application::WrongBehaviour

Group

 

Status

Open

Close date

 

Assigned to