Note that multiple instances is a very different thing from multiple windows. One of them has two processes, the other is one process with multiple windows. They are programmed differently and require different methods to get working.
I would think multiple windows would be the more sane way to go.
@krixano It would be more sane way but currently it is not a priority(as it seems). So allowing to open it one more should help with navigation problem. I don’t know when they will even implement either of those solutions.
Several accounts is actually a really good reason for multiple instances, actually. I forgot about that.
However, by saying it was more “sane” I mainly meant that multiple windows would likely be easier. Multiple Instances have to deal with Inter-process Communication (the multiple instances might have to talk to each other), proper locking and sharing of the file system, etc. It can get complicated very quickly depending on how your application works. While with multiple windows, everything is in one process, so there’s no inter-process communication happening, and the multiple windows can share threads, share open files, share memory, etc.
If the team were to go the multiple instances route, maybe by having a portable version that’s in its own portable folder where the instance exe and data is located, then they would need to make sure the custom local storage path stuff works first, because of course each storage path would be in its own portable folder.
Some of our Nightly Testers are running things in this way to maintain their primary account and use another one for pre-release features. It’s a pretty experimental set up though, which easily presents the risk of data loss if you aren’t attentive, so I can’t advise it.
I was asked to provide a screen recording with a bug report and I actually hesitated as the screencap might show something I do not want to broadcast to you or the internet. Took some extra steps to mitigate but was still hesitating.
Having the ability to simply switch to a plain “tester/proof-of-concept” profile/space/account/session would have removed this problem and as an added benefit for you it would also ensure that no customization is the source of the bug.