@avra
Ok, Lets try this new project group package. (Tested on Lazarus 1.8RC1 - Win32)
Created a new project group. Nice.
Lets create a new project. Hmm, It is not added to current group. You need to add it to group, manually
OK, Lets add it. You need to save it first. Ok, I found its folder on disk even Lazarus knows where it is saved.
Created secondary form. Nope, it is not updated in group. You need to reload group, manually
Try reload ? No! In order to reload you need to save project group first, manually
Click save. Group updated ? Nope. Click reload again...
Created another project. Well, it is not in group, added it to group, manually,
Created a secondary form. Of course it is not updated in group. You need to reload, manually
Removed a secondary from from project. Nope, Its still there in group. You need to reload,manually
Decided to rename main unit, "Save as" in different name. Guess what ? You need to reload, manually
Btw, everytime you reload, project group tree is collapsed and forget where it were, you need to expand projects -and- files nodes everytime, manually.
So you cant use it in comfortable way to navigate between all units. You better continue to use project inspector to navigate between active project's units.
Now, created debug and release build modes for each project and set project1 for debug and project2 to release modes.
Are these reflected in group ? Well, they both have default,debug and release modes in group now but none of them selected.
Try reload ? Nope. They are still unselected. Try compile ? Nope, nothing happens.
It turns out project group has own build mode settings independent from project settings,which you need to select for each project, manually.
Compile by Run Menu, projects settings is in effect, compile by project group, group settings is in effect.
Just a little inconsistency you need to remember...
...
"Find in files" has no option to search all projects.
Change tracking on disk files only works for active project.
Code Browser only works for active project.
ToDo List only works for active project.
...
So, you need to babysit project group on every change for every project and nothing works at group scope. There is no real benefit except building more than
one project at once. Even then it does not comply each project's build modes but it compiles them with it's own mind.
And that is good enough, supported by Lazarus, project group feature for you ? You must be kidding. Really ? I mean, reeeally???
Now, create a new file, write your project's full paths, prefixed by lazbuild, like
lazbuild c:\projects\project1\project1.lpr
lazbuild c:\projects\project2\project2.lpr
save it as a batch file on Windows or insert #!/bin/sh as first line on Linux to build your projects at once and Voila!
There it is. Plus it will adhere your project's own settings. Continue to use Recent Projects on menu to switch between projects and you're done.
You will not really miss any of this "well supported!" group features. Because there is nothing beyond that it provides.
Sorry, truth hurts.
Anyway, whenever I had to argue with 3rd parties on somewhat stupid side-subjects like this I try giving a comprehensive answer and fact-checking it with my limited English and waste a lot of time then I lose my motivation badly to participate on this forum. Silly me.
Therefore I'm out of here once more for a rather long time.
See you later guys, well... maybe