If pressing build-and-run and then switching to a different project while the build is in progress, at the end of the build, the currently selected project will be executed instead of the one that was building.
Confirmed in latest Code::Blocks SVN (10040). I have also noticed this: if I go to project #1 and choose to build and run main.c, then switch to project #2 main.c while it does that, it will build and run project #2 instead of #1. Even weirder, if I go back to project #1, choose build and run, and stay there, it will still build and run project #2. If I manually choose build and then run, it still happens.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Switching project is something that should be disabled during building, but apparently it is not. Until we add code to disable switching project, just remember not to do it while you're building something.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Huh, why would you disable it? That would be a total anti-feature! Some of my builds regularly take upwards of 20 minutes, and it's a huge dent in productivity if I can't work on other projects, including running or debugging or modifying project properties of other projects while one is building.
Locking out features that have no reason to affect the current build is just harming the user experience for no reason whatsoever.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To save you from random problems. If you want to work on two projects simultaneously just start two instances of C::B. There is a setting that allows it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and then switching to a different project while the build is in progress, at the end of the build, the currently selected project will be executed instead of the one that was building.
Confirmed in latest Code::Blocks SVN (10040). I have also noticed this: if I go to project #1 and choose to build and run main.c, then switch to project #2 main.c while it does that, it will build and run project #2 instead of #1. Even weirder, if I go back to project #1, choose build and run, and stay there, it will still build and run project #2. If I manually choose build and then run, it still happens.
Switching project is something that should be disabled during building, but apparently it is not. Until we add code to disable switching project, just remember not to do it while you're building something.
Huh, why would you disable it? That would be a total anti-feature! Some of my builds regularly take upwards of 20 minutes, and it's a huge dent in productivity if I can't work on other projects, including running or debugging or modifying project properties of other projects while one is building.
Locking out features that have no reason to affect the current build is just harming the user experience for no reason whatsoever.
To save you from random problems. If you want to work on two projects simultaneously just start two instances of C::B. There is a setting that allows it.
See ticket 91 for related request.