-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
API: view management API for non-TextEditors #14483
Labels
api
*duplicate
Issue identified as a duplicate of another issue(s)
feature-request
Request for new features or functionality
Milestone
Comments
bpasero
changed the title
feature request: view management API for non-TextEditors
API: view management API for non-TextEditors
Oct 26, 2016
@jrieken fyi |
We have a dup for that but I am not finding it right now |
I have a few markdown extension feature requests / bugs that all depend on this functionality, namely #8581 |
We've got data associated with each opened HTML view, which could be very large. So we'd like to know when the tab is closed (not just deactivated) so we can dispose of it. |
closing as dupe of #15178 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
api
*duplicate
Issue identified as a duplicate of another issue(s)
feature-request
Request for new features or functionality
Request: API support for managing non-
TextEditor
views. The functionality should support:onDidChangeActiveTextEditor
or newonDidChangeActiveView
)visibleTextEditors
or newvisibleViews
([API] Provide Virtual Document in window.visibleEditors or similar #6941)In particular,
previewHtml
should return an object that provides the above functionality,Example use case: I create a preview for each open document of a certain file type. (The preview is derived from the current state of processing the document; not its contents.) Typically, the documents are all on the left column and their previews are on the right. When interacting with the document, its associated preview should become visible (without receiving focus); moving to a different column than the document itself if necessary. Without this kind of functionality, it easy for the user of my extension to become lost and confused when interacting with multiple documents.
The text was updated successfully, but these errors were encountered: