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

Reset View Locations command only puts views back into their panel of origin, but ignores order and height #162366

Closed
Tommycore opened this issue Sep 29, 2022 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality workbench-views Workbench view issues

Comments

@Tommycore
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.71.2
  • OS Version: Win 10 Pro x64 version 1909

Steps to Reproduce:

  1. Move views into different panels, resize them and reorder them.
  2. Call the View: Reset View Locations command via command panel.

Expected Behaviour:

  1. Views are being sorted back into their panel of origin.
  2. Views are scaled back to their original size. If two views did originally take up equal space, they should do so again. If a panel was retracted before, it should be retracted again.
  3. Views are being put into their original order.

Actual Behaviour:

  1. All views are being put back into their panel of origin.

If this behaviour is by design, then I'd like to turn this bug report into a feature request. As an extension developer it would be incredibly helpful to be able to see the layout of my views like someone who loaded the extension for the first time would. As suggested by alefragnani here, this might be a bug with the new size attribute for views though.

@sbatten
Copy link
Member

sbatten commented Oct 21, 2022

This is by design, so this would be a feature request to have the ability to reset your extension views. There are 2 sides to this, both from the user and from an extension authors perspective. Usually we don't want the extension author to make these decisions for the user, but make view management a user choice.

@sbatten sbatten added feature-request Request for new features or functionality workbench-views Workbench view issues labels Oct 21, 2022
@vscodenpa vscodenpa added this to the Backlog Candidates milestone Oct 21, 2022
@vscodenpa
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa
Copy link

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa
Copy link

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Feb 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality workbench-views Workbench view issues
Projects
None yet
Development

No branches or pull requests

3 participants