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

package explorer indent horrible to read #76722

Closed
judos opened this issue Jul 5, 2019 · 2 comments
Closed

package explorer indent horrible to read #76722

judos opened this issue Jul 5, 2019 · 2 comments
Assignees

Comments

@judos
Copy link

judos commented Jul 5, 2019

  • VSCode Version: 1.36.0
  • OS Version: Win10 Pro

Steps to Reproduce:

  1. Open workspace folder
  2. Look at explorer on the left side

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

To give an impression what the user is looking at I marked the left-most visible pixels for each folder with a red line. As you can see subfolders and files have a different indentation. This is very confusing and gives the user difficulties to group the perceived elements. Probably also why a lot of tickets are created where users want to change indentation etc: #17777, #35447, #76276

indent1

As proposal it would be good to make the arrow icon of the subfolder the same size as the other icons such that the icons actually show up at the same indentation.

@joaomoreno
Copy link
Member

The workbench.tree.indent setting lets you control indentation. The workbench.tree.renderIndentGuides setting lets you display indent guides.

@judos
Copy link
Author

judos commented Jul 10, 2019

Great but not what I asked.
The issue is that the icons are not aligned and that makes the UI very hard to read. Even with the indent and indentGuide lines. If the icons would be correctly aligned you would probably also get less people asking about changing indent and showing indent lines always.

grafik

@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants