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

Extensions: Query UI State #23122

Closed
hoovercj opened this issue Mar 23, 2017 · 2 comments
Closed

Extensions: Query UI State #23122

hoovercj opened this issue Mar 23, 2017 · 2 comments
Labels
api feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code

Comments

@hoovercj
Copy link
Member

Extensions need to be able to query the UI State. Is the sidebar open, which viewlet is visible, are there multiple editor columns, in the bottom section is the terminal, output, or problem viewer active, etc.

For example, I have a small Auto-Collapse Explorer extension that I'd like to publish that needs this functionality.

When the active editor changes, the extension collapses the explorer and then focuses the active editor.

This should only happen if:

  • There is an active editor (already possible to check)
  • The sidebar is open (not currently possible)
  • The explorer widget is open in the sidebar (not currently possible)

As the sidebar opens up to more viewlets (different SCM views, extension provided viewlets, etc.) this will become even more useful to extension developers.

@bpasero bpasero added api feature-request Request for new features or functionality labels Mar 27, 2017
@bpasero bpasero removed their assignment Mar 27, 2017
@hoovercj
Copy link
Member Author

Are these values that would be appropriate for VS Code to store in the global or workspace state on the extension.context object? That would prevent the need for adding new API surface for what is effectively "state"

@mjbvz mjbvz added the *out-of-scope Posted issue is not in scope of VS Code label May 17, 2018
@vscodebot
Copy link

vscodebot bot commented May 17, 2018

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. 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 May 17, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

3 participants