Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Click task icon on second virtual desktop to switch to active app in other v-desktop in Windows #58978

Closed
CaptainN opened this issue Sep 19, 2018 · 3 comments
Assignees
Labels
electron Issues and items related to Electron *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@CaptainN
Copy link

If I have VSCode running a second virtual desktop, and I click on the VSCode icon on the first virtual desktop, it should switch to the other virtual desktop, and focus the already running copy.

What it does now is start a second copy on the current virtual desktop, which is sometimes useful, but is useful less often than switching to the right virtual desktop would be. If there are multiple copies on multiple v-desktops, it might be useful to cycle through all running copies.

For context (skip this if you don't have time) - I came from macOS back to Windows - on macOS I have tended to use multiple full screen apps and switch between them using either the gesture (which thankfully also exists on Windows now - great!), or by clicking the launcher icon when using a non-swipable interfaces like a scroll mouse. I'd actually prefer to have a standalone precision track pad (similar to Apple's standalone magic track pad), but since that doesn't seem to exist for Windows (send this request to the Surface Book team!), a simple way to click the icon to switch would be a fine substitute. I'm using the key command - Windows + control + arrows - but that requires 2 hands on most keyboards, which have the windows keys on the left, and the arrows on the right.

@vscodebot
Copy link

vscodebot bot commented Sep 19, 2018

@CaptainN
Copy link
Author

Hmm, it seems #35240 and #14619 are saying it used to do what I'd like it to do, but then it was changed to the current (less useful IMHO) behavior. Can there be an option to put it back?

@bpasero bpasero added upstream Issue identified as 'upstream' component related (exists outside of VS Code) electron Issues and items related to Electron labels Sep 21, 2018
@bpasero bpasero added the *out-of-scope Posted issue is not in scope of VS Code label Oct 9, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 9, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
electron Issues and items related to Electron *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants