Vscode: Middle mouse click on taskbar icon doesn't open a new window
- VSCode Version: Code 1.6.1 (9e4e44c19e393803e2b05fe2323cf4ed7e36880e, 2016-10-13T16:21:53.542Z)
- OS Version: Windows_NT ia32 10.0.14393
- Extensions: abotteram.typescript-react-snippets-0.1.9, hars.CppSnippets-0.0.5, lukehoban.Go-0.6.44, ms-vscode.cpptools-0.9.2
Steps to Reproduce:
- Middle click on running VS Code icon on the taskbar, it doesn't open a new window like many programs
- You can open a new window by right clicking the icon and choosing "New Window"
cozzbp
All 13 comments
Related: When working with multiple workspaces, clicking on VS Code in the taskbar on a workspace where it hasn't been started yet switches to a running instance on another workspace instead of starting a new one.
jhasse
on 18 Oct 2016
This has to be fixed, very annoying now that Windows finally has multiple virtual desktops natively.
VS Code should automatically open a new window upon execution. This way, Windows will take care of activating an existing window unless shift is held while clicking the button, or, opening a new VS Code window.
peredin
on 10 Nov 2016
It may actually be a problem with electron apps in general. Postman also exhibits this behavior.
cozzbp
on 10 Nov 2016
I think it should be done by setting System.AppUserModel.RelaunchCommand with -n argument.
It will need to be implemented in Electron (like e.g. jump lists).
the-ress
on 10 Nov 2016
bpasero
on 3 Apr 2017
- VSCode Version: Code - Insiders 1.12.0-insider (d8a1d8b8a7c886547ba6bc0d81fc2ff639d4c9f5, 2017-04-27T06:12:15.095Z)
- OS Version: Windows_NT ia32 10.0.14393
- Extensions: none
'New Window' works, but middle click and Shift + left click still don't.
chrmarti
on 27 Apr 2017
I've just finished some investigation into this. It works when launch VSCode using scripts\code.bat, but not when I build VSCodeSetup.exe and install it.
The shortcut in start menu (which has the same AppUserModelID as the window) seems to take priority over the RelaunchCommand value. (I couldn't find any way to override this.)
AppUserModelID of the shortcut and the window needs to match so they share one MFU list and jump list.
Only solution I can think of is to add the -n argument to the start menu shortcut too.
the-ress
on 27 Apr 2017
I am a bit confused, I could swear I tested this. But probably only from a local built VS Code, never when going through the setup. Too bad...
bpasero
on 28 Apr 2017
Had similar issue with sublime, managed to get it working by adding the -noframemerging switch to the target of the shortcut. Right click on shortcut to vscode, go to shortcut tab and in target add -noframemerging after the path to the executable (should be outside the quotes).
todorm85
on 5 Dec 2017
How is this still a thing?
dmrickey
on 1 Mar 2018
@the-ress I cannot really explain it but with our current insiders release, middle-click on the taskbar opens a new window for me (stable does not work).
Can others try to reproduce this with our insiders: https://code.visualstudio.com/insiders/
I am very confused what change could have an impact :-/
bpasero
on 7 Mar 2018
Wow, now I am back to having it NOT working in insiders, this is very weird....
bpasero
on 7 Mar 2018
bpasero
on 9 Mar 2018
Related issues
sirius1024
路
3Comments
trstringer
路
3Comments
DovydasNavickas
路
3Comments
VitorLuizC
路
3Comments
vsccarl
路
3Comments
Most helpful comment
Had similar issue with sublime, managed to get it working by adding the -noframemerging switch to the target of the shortcut. Right click on shortcut to vscode, go to shortcut tab and in target add -noframemerging after the path to the executable (should be outside the quotes).