-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Refine debug toolbar #52490
Comments
In June we have improved the positioning of the "floating" toolbar. |
I'm running Every time I open VSCode I have modify the local style on the "debug-actions-widget" to change |
@pklapperich as always the new feature is available in the current Insiders release (1.25.0) and it will become available in the upcoming stable June release. |
Why in the world is it floating in the first place? I never could understand that choice and now the fix is to make it even more "floaty"?! |
@WhatFreshHellIsThis if you don't like the floating bar, you can dock it. |
Cool, thank you @weinand I didn't know that, my work life just got a tiny bit more pleasant! I still wonder at the mystifying choice to float it at all. I've used VSCODE with many different languages and environments now and I still don't see a use-case for it other than to annoy people but maybe that's just me. |
I've tried to compile issues and proposals from #2513 and #9093:
Today VS Code supports two locations:
"floating" debug toolbar issues:
"docked" debug toolbar issues:
Proposed Debug Bar locations:
Important requirements:
My take:
The two important requirements could be easily addressed by a global toolbar, but VS Code doesn't provide one.
Since it is difficult to find a good solution that obeys both requirements, I propose a two-pronged approach:
improve "floating" toolbar (which will continue to be the default):
improve "docked" toolbar (which is most likely covered by Show debug sessions under a new split view section #49881):
Let's start by improving the "floating" toolbar.
The text was updated successfully, but these errors were encountered: