search

godotengine / godot

Godot Engine – Multi-platform 2D and 3D game engine
https://godotengine.org
MIT License
90.57k stars 21.09k forks source link

Step Over in Debug is hard to click due to inspector resizing on every step #33474

Open ondesic opened 4 years ago

ondesic commented 4 years ago

3.2.alpha.calinou.af4fd9de9

Here is a video of what happens when you try to step through code while debugging. The inspector panel annoyingly resizes in between each click. This doubles the time it takes to step through the code.

Also, as you can see, if you are clicking fast the buttons move so you click "Step In" instead of "Step Over"

StepGlitch.zip

Calinou commented 4 years ago

This is likely not the debugger's fault, but rather the inspector's as its width changes if properties have long names.

ondesic commented 4 years ago

when going for line to line, the inspector panel clears itself (and changes width) then repopulates itself. Can something be done to preserve the panel width in between each step?

ondesic commented 4 years ago

I just tested this will a small project that has no variables longer than 3 letters. Even when the inspector has not properties with long names being displayed, it still changes size with each "step over" click. This sure makes debugging hard. Hope this can be fixed like in 3.1

KoBeWi commented 3 years ago

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

If yes, please ensure that an up-to-date Minimal Reproduction Project (MRP) is included in this report (a MRP is a zipped Godot project with the minimal elements necessary to reliably trigger the bug). You can upload ZIP files in an issue comment with a drag and drop.

Calinou commented 3 years ago

I suppose we can fix this by aligning the debugger buttons to the left instead of the right. Therefore, when the inspector changes its size due to children elements having a large rect_min_size, the buttons' positions will remain the same.

The downside of moving the debugger buttons to the left is that your mouse will have to travel more between the local variable inspector and the debugger buttons. I'm not sure how much of a problem this will be in practice, considering that you should generally use keyboard shortcuts if you want things to go quickly :slightly_smiling_face: