Morten: Is there any chance, this patch can get into trunk?
Well in fact I've maintained this patch during the time and also using it.
The reason why I am not committing is the following serious drawback:
Well you have all your changes in the layout file now, but also the pointer to which project is the active one.
If you
do commit the layout file you have the same thing happen: This will change often.
If you
do not commit the layout file you are missing to point to the active project so C::B would set the first one as active which will break your compilation most likely if you do a clean checkout (take project dependencies into consideration). Also in this case I believe the
active project in a mandatory information as it controls the build process and therefore should really remain in the workspace file or somehow provided to the developer. Probably a "default active project" can remain in the workspace and a "current active project" could be in the layout. But then: When and how to update the "default" one?!
I don't have a good idea how to resolve this so far... if someone has - step forward.
For the moment - always using forward slashes (the unix way) in the project and workspace files (so partially applying this patch) might be something better.