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

Don't close Commands View on losing Focus #448

Closed
prasannavl opened this issue Nov 22, 2015 · 4 comments
Closed

Don't close Commands View on losing Focus #448

prasannavl opened this issue Nov 22, 2015 · 4 comments
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@prasannavl
Copy link

Closing Commands View on losing focus is annoying, particularly when installing or searching for extensions, and commands that are not instantaneous.

Please stop the commands view from closing itself when the window loses focus.

@bpasero
Copy link
Member

bpasero commented Nov 23, 2015

As designed, however we also see the issue that extensions should go into a more stable view and not quick open.

@prasannavl
Copy link
Author

I see this as future solution to the extensions issue: #637

However, while I understand its "as designed", I really see no good reason why it is really designed that way. Is there a reason why the command window has to be closed when the window loses focus?

I see this as something that seems to be inherited from Atom. The "ext install" is just one scenario that highlights this problem. But often switching between windows, and losing the command window is extremely frustrating. Just changing this design decision will not just enable the multi-taskers to work with ease, but also provide a temporary mitigation to the "ext install" problem until the new UI is designed (which I surmise will take quite a while looking at the state of things).

Could this be reconsidered?

@bpasero
Copy link
Member

bpasero commented Feb 9, 2016

#444

@bpasero
Copy link
Member

bpasero commented Aug 15, 2016

This is coming for August via #444.

@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Aug 15, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants