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

Debugger name button width / ensuring the whole widget has static width #8

Closed
Spown opened this issue Mar 4, 2018 · 4 comments
Closed

Comments

@Spown
Copy link

Spown commented Mar 4, 2018

As per #4

Can you make the button assume the longest debugger name (i.e. in case of compound debuggers, make it's width static as long as no new debuggers are added or present ones stopped), so that the following control buttons wouldn't jump left and right?

Thank you.

@fabiospampinato
Copy link
Owner

VSC still doesn't expose enough information about compound debugging for implementing this (microsoft/vscode#30810).

You can, however, put "statusbarDebugger.template": "$(bug)" in your settings in order to hide the name entirely, or, using this extension, you can assign a fixed width to that button.

@Spown
Copy link
Author

Spown commented Mar 4, 2018

Custom CSS and JS Loader introduces too much enthropy. Can you maybe add a setting? something like "statusbarDebugger.mainButtonMinWidth": number?

@fabiospampinato
Copy link
Owner

VSC provides no API for doing this thing, the only way I could implement it would be by basically doing what "Custom CSS and JS Loader" does, but I don't see the point in that.

Another option you could try is to rename your configurations, adding some non-breakable whitespace characters at the end until they all occupy the same width, maybe that could work.

@Spown
Copy link
Author

Spown commented Mar 4, 2018

Another option you could try is to rename your configurations, adding some non-breakable whitespace characters at the end until they all occupy the same width, maybe that could work.

The font used there isn't monospace, so it'll be jumping regardless. Oh well, thanks anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants