Second instances are opened when they should not be

[jromero-irt]

Description
The app is not handling second instances correctly.

• Version: latest

Steps To Reproduce

1. Open an instance of Lichtblick (this can be done using the UI or terminal).
2. Open a terminal and try to open a new instance of Lichtblick without using the --force-multiple-windows flag.
3. The stdout will show that another instance is already running, and the process will finish, but the instance will remain open.

Expected Behavior
No more instances of the app should open if no flag is passed or no files/deep links are opened.
For more information, check the PR that introduced the new flag #600

[aneuwald-ctw]

Hey @jromero-irt, thanks for reaching out!

So, the thing is (this came from the original fork) the implementation was trying to replicate the behavior when you try to open a new Liichtblick with an MCAP as argument, it tries to render in the same instance that it is already opened. But when you open without MCAPs as argument (let's say, a double click from your UI), it assumes that you want to open a new one.

We added the flag to force that even with an MCAP as argument, you can open more than one instance (eg. to compare two different MCAPs). Originally the second one would close and the first one would load the mcap passed to the second instance (kinda confusing, right?)

But we decided to let the original behavior and just add the flag to this specific use case.

Is it a problem in your use case? Or is it just a strange behavior that you noticed and wanted to report? We can definitely find a solution for you!

Cheers,
Alex

[carolinabamorim]

HI @jromero-irt was this fixed with this merged PR: #683?