Running multiple instances doesn't seem to work

[sparhawk]

I tried to run a second instance of CB with a different project. I disabled "Settings->Environment->Allow only one instance".

When I doubleclicked on the projectfile, CB just hung and didn't respond anymore. I noticed that this "Settings->Environment->use an already running instance" doesn't really make sense when I want to run a second instance and disabled it. CB didn't get stuck but a second instances is also not started. It just reuses the already open one.

Of course I restarted CB when changing these settings.

Am I missing something or is this a bug?

[oBFusCATed]

You have both disabled. This config works fine, I'm using it for almost forever.
What OS and C::B versions are you using?

[sparhawk]

You have both disabled. This config works fine, I'm using it for almost forever.

And how do you start a new instance? It definitely doesn't work for me. CB behaves as if I selected only one instance being allowed, and if I have the "use already running" enabled then it just hangs when doubleclicking on a projectfile.

What OS and C::B versions are you using?

Windows 7, CB 13.12 Build Dec 27 2013 12:58:38 - wx2.8.12 (Windows unicode) 32 Bit.

Actually I found another bug related to this. I opened the "Project->rightClick->Build options..." and while this dialog was opened, I double clicked on a project file. The Dialog from the old project stayed open, while the new project was loaded in the main window (still only one instance though).

[oBFusCATed]

Uncheck both checkboxes, stop C::B. Start C::B by clicking on the exe, start another version again by clicking on the exe.

If you're telling us that it doesn't start another instance if you click on a cbp file, then this is another use case probably.
Please describe the exact steps to reproduce the problem you're seeing.

[sparhawk]

You are right. When I click on the CB exe to run it, then I can start several instances.

What I did was that I had CB open with one workspace. I double clicked on another workspace file "project2.workspace" in which case CB reuses the current instance instead. The same happens when using the project2.cbp file instead of the workspace file.

[oBFusCATed]

Someone familiar with the DDE code should tell if this is bug or expected behaviour.

[sparhawk]

Any news on this?