Skip to content

Debug actions pane often blocks file names #2513

Closed

Description

Currently the debug actions pane is always displayed at the top center position. This often blocks the file names.

image

It would be helpful to find a better place for the pane or add the ability to move the debug actions pane.

Activity

  1. added
    debugDebug viewlet, configurations, breakpoints, adapter issues
    feature-requestRequest for new features or functionality
    on Jan 29, 2016
  2. jtlowe commented on Oct 14, 2016

    @jtlowe

    Yes please! It would be great to have this in its own toolbar. I'm constantly having to move it out of the way when trying to switch tabs.

  3. jtlowe commented on Oct 14, 2016

    @jtlowe

    Possibly something like the image below, that would only appear when in debug mode.

    debugactionpanel_1

  4. kmudrick commented on Apr 12, 2017

    @kmudrick

    I'd love to see it be moveable (more than left to right), or in the debug pane itself. This is pretty painful as is being locked on top of the file tabs.

  5. isidorn commented on Apr 13, 2017

    @isidorn

    Assigning to april to investigate a better solution. Though not making gurantees that this gets fixed in april.
    fyi Steven Clarke (@stevencl)

  6. stevencl commented on May 10, 2017

    @stevencl
    Member

    Jamie Young (@jamiedawsonyoung) - would love to hear your thoughts on this.

  7. 51 remaining items

  8. mikeseese commented on May 3, 2018

    @mikeseese
    Contributor

    I'm sorry, but I think we need to stop complaining and go ahead and put in the work. I don't see any of you stepping up to the plate and submitting a PR as Isidor Nikolic (@isidorn) recommended in February.

    Sure, I'm not sure why this one issue has fallen through the cracks, but I feel as developers we all know what it's like to be "too busy" to work on something that isn't in our priority list, or our bosses priority list. We all probably are just going to respond "Mike, we don't have time to do this, this is Microsoft's job." Well they are busy too, and try to release a stable product monthly for the entire world to use.

    I will try to put in some time the next two weeks to submit a PR if no one else steps up to the plate, merely because I'm tired of hearing all of the complaints.

  9. mikeseese commented on May 3, 2018

    @mikeseese
    Contributor

    I've submitted 2 PRs for further discussion with VSCode maintainers/Isidor Nikolic (@isidorn). While #49097 is a readily available PR which allows vertical dragging, I prefer the other proposed solution in #49099 which will need further discussion in terms of implementation. I will push to have some sort of solution merged for the May or June milestones.

  10. JeanClaudeCottier commented on May 3, 2018

    @JeanClaudeCottier

    I've been using Fabio's extension for months (THANK YOU FABIO). Most of the time, I'm using the keyboard shortcut anyway. I switch off the original and awful (yes awful) debugger tab and never looked back. I made VSCode my main platform for development (I wouldn't have without the extension). I feel the pain for the people that can't use it. I can't believe this hasn't been fix yet. VSCode is a great product that I'm promoting all the time. But the debug tab!!!! What are you waitting for guys? No excuses, for such a critical feature.

  11. kletkeman commented on May 3, 2018

    @kletkeman

    Mike Seese (@seesemichaelj) I agree that the whinging is probably best replaced with action. My excuse is having worked into the wee hours for too many days in a row, shuffling the debug tab back and forth as I stop, start, restart, stop, start, restart a couple of micro-services ... it gets a little old ... I'll take a look at Fabio's extension, thanks for the tip Jean-Claude Cottier (@JeanClaudeCottier)

  12. bakasmarius commented on May 4, 2018

    @bakasmarius

    Mike Seese (@seesemichaelj) I agree with you, but when I decided to try and make a PR myself I went to read about how to set up VSCode for developing it... It surprisingly has quite a lot of steps, so I decided to leave it for later "when I have more time", so like never :D But I guess I should just do it today and get over with it :)

  13. mikeseese commented on May 4, 2018

    @mikeseese
    Contributor

    I appreciate the initiative Marius (@bakasmarius)! I went ahead and created PRs (see my last comment) so at this point it would be duplicating work, and much of it relies on the outcome of UX meetings.

  14. isidorn commented on May 10, 2018

    @isidorn

    Thanks for the feedback and for opening PRs with great ideas.
    After discussion we decided to introduce the following setting
    "debug.toolbar": "float"|"dock"|"hide"

    The default is like before that the debug toolbar is floating, however it can now be docked to the debug viewlet.
    debug.hideActionBar is now deprecated and we will no longer support that setting in 2 milestones.

    Feedback is welcome, especially on naming of settings.
    What I still plan to investigate if possible is to add some action in the toolbar to dock it directly from there.

    fyi Andre Weinand (@weinand) Alex Ross (@alexr00)

    debugtoolbar

  15. fabiospampinato commented on May 10, 2018

    @fabiospampinato
    Contributor

    That's better, thank you, but why not putting the commands in a secondary line/toolbar? Like this:

    Secondary toolbar

    The current solution isn't great for compound debugging, this sidebar looks absolutely massive to me:

    normal

    It can be resized, but then I lose the name fo the view ("DEBUG"), the name of the launch configuration gets cropped, and even the "more" button gets hidden.

    resized

    Putting this actions on a secondary line/toolbar just seems a better solution to me.

  16. mikeseese commented on May 10, 2018

    @mikeseese
    Contributor

    I definitely agree with Fabio Spampinato (@fabiospampinato).

    Further, you lose the launch configuration drop down. There are cases where you start debugging and then want to run another launch configuration. You can't press F5 because your selected configuration is already running and I believe combining the multi-process dropdown and launch configuration dropdown into one will be nonintuitive and a clutter.

  17. locked and limited conversation to collaborators on Jun 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

debugDebug viewlet, configurations, breakpoints, adapter issuesfeature-requestRequest for new features or functionalityon-testplanrelease-notesRelease notes issues

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions