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

Debug toolbar custom positioning #9093

Closed
JoshMcCullough opened this issue Jul 11, 2016 · 21 comments
Closed

Debug toolbar custom positioning #9093

JoshMcCullough opened this issue Jul 11, 2016 · 21 comments
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality ux User experience issues
Milestone

Comments

@JoshMcCullough
Copy link

  • VSCode Version: 1.3.0
  • OS Version: Windows 10

Happy that I can now move the debug toolbar in the the 1.3 update! However, I think it is better suited for the sidebar, as it is often/constantly in the way.

image

Alternately, it could be attached to the debug console.

image

@weinand weinand added the feature-request Request for new features or functionality label Jul 11, 2016
@teyou
Copy link

teyou commented Jul 12, 2016

Yeah, sidebar would be an good option.
Especially after 1.3 (tab stacks feature) released, often find myself keep adjusting the debug toolbar position

@mauriliofilho
Copy link

Find it more convenient to put down the flaps open, keeping the standard for debug bar for all editors, eg Atom and Sublime

@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Jul 19, 2016
@isidorn isidorn added this to the Backlog milestone Jul 19, 2016
@isidorn isidorn added the ux User experience issues label Jul 19, 2016
@bgashler1
Copy link
Contributor

UX meeting notes
We could do a quick fix on this, but what we’re seeing is just one manifestation of a larger problem: our global commanding patterns need some work, as does our debugger UX. We will instead move to improve these overall experiences, which will in turn address this problem.

@calbot
Copy link

calbot commented Mar 24, 2017

Anyone who wants a quick fix for your own productivity. Use command palette "Developer: Toggle Developer Tools" to use chrome developer tools. Then find the debug widget and change the top to 90px to shift it below the tabs and the find box. -5px is also nice :) ... I didn't like it covering the tabs.

screen shot 2017-03-24 at 12 04 48 pm

@ronnyek
Copy link

ronnyek commented May 25, 2017

I think this is a huge problem that makes me want to just avoid vscode for debugging. I'd recommend making the debug tools a part of a toolbar and persist across the different tab views. (if I am in explorer or plugins, I'd still be able to see the start debugging / stop etc.

@will-l-h
Copy link

Would be great if there was some progress on this. The UX of hiding other controls under a floating debug actionbar is a bit crazy.

So many other great aspects to VS Code, why has this languished for a year?

@catdadcode
Copy link

catdadcode commented Jun 24, 2017

Any updates on this? Really hate constantly dragging the floating action bar around as I navigate a full screen of tabs. Can extensions modify VSCode's markup? If so I might look into writing an extension that simply moves the widget into the debug pane for now. It's definitely a pet peeve.

@isidorn
Copy link
Contributor

isidorn commented Jun 26, 2017

We will look into improving this experience this in the next couple of iterations, it is not on our plan for this milestone.

@mattacosta
Copy link
Contributor

mattacosta commented Jun 29, 2017

As I usually have quite a few tabs open when debugging, I was thinking more along the lines of:

debug-toolbar-800

If the side panel was closed, then it could fallback to the default behavior.

@catdadcode
Copy link

catdadcode commented Jun 29, 2017

That's exactly what I was thinking. I'd really love it if it docked into the debug pane or debug console pane.

@fabiospampinato
Copy link
Contributor

Alternatively we could make it float like the search widget, but perhaps anchored at the bottom, somewhat more consistent and out of the way, something like this:

screen shot 2017-07-16 at 01 39 55

@fabiospampinato
Copy link
Contributor

Even moving the bar to the statusbar sounds like a saner idea to me:

StatusBar Debugger

If you want to check it out for yourself I've just published the extension.

@ronnyek
Copy link

ronnyek commented Jul 16, 2017

I think that extension looks better than nothing.... But just kind of demonstrates the need for a proper toolbar... The status bar realestate is already limited... And with many of the extensions also pushing their ui to status bar (because that's all that's available) it's getting out of hand

@endquote
Copy link

endquote commented Aug 6, 2017

I'm thinking what @mattacosta is thinking.

Also, when debugging multiple processes, I'd like multiple debug bars, instead of one debug bar with a dropdown to pick the process.

@wyckster
Copy link

What @mattacosta proposed is great and that's what I'm hoping for. I think it can easily be allotted some vertical real estate at the top of the debug panel of the side bar while debugging.

Wherever it goes, it shouldn't be floating. Rather than cover other controls, it should displace them so it can be docked into place somewhere without covering up other tabs or toolbars. I'd even be fine if it sat to the left of the tab bar (outside the side bar) and displaced tabs to the right - sharing space currently allocated to the tabs. e.g.:

toolbaridea

@mhillct
Copy link

mhillct commented Sep 18, 2017

I've settled on placing it over the DEBUG start button:
image

@Spown
Copy link

Spown commented Sep 20, 2017

How about just unanchored free floating option?

@Spown
Copy link

Spown commented Sep 20, 2017

also this issue is apparently a dup of #2513

@isidorn
Copy link
Contributor

isidorn commented Sep 20, 2017

Yeah, closing as dupe of #2513

@isidorn isidorn closed this as completed Sep 20, 2017
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 20, 2017
@alexmolodchikov
Copy link

Hey @bgashler1 @isidorn
Any updates on this issue? Seems like it's been discussed for a while and the demand is there.

@lazysergey
Copy link

I hate this toolbar so much, finally ended up turning it off completelly by adding
"debug.hideActionBar": true to User Settings

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality ux User experience issues
Projects
None yet
Development

No branches or pull requests