Open lukostello opened 4 years ago
because everyone debugs.
I wouldn't say so :slightly_smiling_face:
Either way, you can already disable all breakpoints by clicking the button with a breakpoint appearance in the debugger tab (it'll have a "strikethrough" overlay when disabled).
but that isn't very helpful when I want to change what it is that I am debugging or have finished debugging a specific class
There's already such option under Go To -> Breakpoints (shortcut is Ctrl + Shift + F9).
excellent. Although I think it makes more sense to put the breakpoints on the debug drop down as well as have a script specific alternative
Describe the project you are working on: sokoban like with twisty puzzle mechanics
Describe the problem or limitation you are having in your project: irritated by having to manually uncheck every breakpoint after debugging
Describe the feature / enhancement and how it helps to overcome the problem or limitation: in the debug drop down, have 2 options
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
If this enhancement will not be used often, can it be worked around with a few lines of script?: will be used often, cannot be worked around Is there a reason why this should be core and not an add-on in the asset library?: because everyone debugs.