I like this IDE package since it helps me group projects belonging to an application (executable & libraries, for example). But it has some inconsistent behaviour that sometimes makes it hard to use in (my) every day use.
I sometimes open another project that is not part of the project group, and then this behaviour occurs:
- I press F9 (to run), and the current (non-group) project compiles and runs.
- I press Ctrl+F9 (to compile), and the top/active project of the project group compiles.
In IDE options under Key Mappings, there is no special project group stuff listed.
I have to admit that pressing Ctrl+F9 is part of my workflow to test if code can be compiled, even if I don't want to run it right away, so this is causing confusing and delays often.
I think that is part of the
Compile and Build compile target option in
Tools -> Options -> Project Groups - because if I disable it, it seems to work as intended (by me).
To get a more consistent behaviour, I guess in projectgroupeditor.pas, TProjectGroupEditorForm.BuildExecute() and .CompileExecute() , it needs to be checked if the current project is part of the project group before running Perform()?
Recent
