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

Hidding a Split View does not call setVisible(false) on the view #42978

Closed
isidorn opened this issue Feb 5, 2018 · 4 comments
Closed

Hidding a Split View does not call setVisible(false) on the view #42978

isidorn opened this issue Feb 5, 2018 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug layout General VS Code workbench layout issues verified Verification succeeded
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Feb 5, 2018

  1. Set a breakpoint here
  2. Using the context menu hide the OPEN EDITORS view in the explorer viewlet, notice the breakopint is not being hit
  3. Using the context menu bring back the OPEN EDITORS view, notice the breakpoint being hit

I would expect the setVisible(false) to be called once a view is being hidden.
I have quite some layout optimization code which is depended on the fact if the view is hidden or not. And my optimisations do not seem to work since the view is not aware it is hidden.

@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Feb 5, 2018
@sandy081 sandy081 added this to the February 2018 milestone Feb 6, 2018
@sandy081 sandy081 added the layout General VS Code workbench layout issues label Feb 6, 2018
@sandy081
Copy link
Member

When a view is hidden, it will be removed from split view. When it is shown again, it will be created again and added to split view.

Hence the view has to be disposed when it is removed from the split view.

@isidorn
Copy link
Contributor Author

isidorn commented Mar 1, 2018

I can reproduce this using the exact steps I provided in the original comment

@isidorn isidorn reopened this Mar 1, 2018
@isidorn isidorn added the verification-found Issue verification failed label Mar 1, 2018
@sandy081
Copy link
Member

sandy081 commented Mar 1, 2018

@isidorn As mentioned in comment here I am disposing the view when it is removed. So I do not think it is required to call setVisible(false) if it is getting disposed.

image

@sandy081 sandy081 removed the verification-found Issue verification failed label Mar 1, 2018
@sandy081 sandy081 closed this as completed Mar 1, 2018
@isidorn
Copy link
Contributor Author

isidorn commented Mar 1, 2018

@sandy081 ok, makes sense, sorry for the confusion. Verified it gets disposed

@isidorn isidorn added the verified Verification succeeded label Mar 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug layout General VS Code workbench layout issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants