Hmmm, opening file F in project P1 triggers a project change to project P2 but keeping file F open (and did it actually get opened in P1?).
Maybe what you need is to capture the open _before_ it happens, so you can stash the filename, switch projects and then open the file in the right one.
No, not 100% correct. Lets imagine the following situation: - The workbench gets opened - The user start to work on project A, some files of project A are opened - In the Workbench sidebar the user later clicks on a file of project B to open it - This causes a switch to project B: all open files get closed and only the file from project B is opened
I do not want that behavior and it does not happen if ProjectPrefs item ```project_session``` is disabled. So I shortly disable it and then restore the old value.
If I work with multiple projects it's IMHO likely that I maybe just want to have a look at some header file of a project B without closing all open files from other projects A, C ....