Fixed single desktop app instance handling. #9958
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Windows, launching a second instance didn't even reach the lock acquisition - the application crashed earlier. Now there are no console errors when launching the second application. And there's no window flickering when selecting jump list elements. The main window is also correctly displayed when launching a second instance.
In start.ts, the real changes are only at the beginning of the file. Everything else that was touched is just indentation, in order to 'wrap' all the code into a function.
Application startup and quit logic improvements:
app.requestSingleInstanceLock()) and related quit logic to the top of the startup file, ensuring the application quits early if another instance is running. ThequitApplicationfunction is now used consistently for quitting the app. [1] [2] [3] [4]app.quit()to use the newquitApplicationfunction, ensuring consistent handling of theisQuitingflag across the codebase. [1] [2]Other improvements:
desktop/src/main/windowsSpecificSetup.tsby replacing areturnstatement with abreakin a switch-case default clause for better code clarity and correctness.