Extreme frustration with how godot editor deals with braces.

dotted

99.999999% of the time automatic closure of braces and the very annoying habit of "disappearing" key presses of close brace when I am trying to close off an opening brace is simply bringing me to tears, because 99.999999% percent of the time I am typing a function in front of existing calls and statements and then closing them off.

The ensuing Charlie-Foxtrot means I spend like a minute simply trying to get all the braces closed. This stuff doesn't happen in vi.

Is there no way to disable this behavior?

DaveTheCoder

There's a setting:

Editor >> Editor Settings... >> General >> Text Editor >> Completion >> Auto Brace Complete

dotted

yep that did it. thanks!

although I'd vote it most useless feature or buggiest in the engine.

DaveTheCoder

The feature is annoying.

What would be useful is a find-matching-delimiter feature that some other editors have. If the cursor is next to a brace, parenthesis or bracket, the matching delimiter is highlighted.

dotted

yup 100%

DaveTheCoder

Do you know if a find-matching-delimiter feature is planned for 4.0? If not, I suppose the place to suggest it is at https://github.com/godotengine/godot/issues ?

Megalomaniak

Probably the proposals tracker actually: https://github.com/godotengine/godot-proposals/issues

dotted

Oh I could sprinkle the issue tracker with about 2 or 3 UX situations that I still find maddening, like how clicking to place a cursor on entry fields in the inspector is too damn picky. Often, I am inserting a minus sign or changing one digit and godot editor is very fussy compared to other IDEs.

In 4 the are going to make the side panels window-able, but still when transitioning from and to debugging the editor constantly chooses which tab is presented, like switching from console to debugger or switching away from the profiler or monitor. It's a drag on workflow.

Ertain

With respect to the "matching delimiter" issue: the editor does do matching for square brackets and parentheses. However, it only underlines them; it doesn't highlight them.

DaveTheCoder

You're right! The editor does that for braces too. How did I miss that?

I'd prefer that the whole character be highlighted. That underline is hard to see, especially for square brackets.

I suppose it's not as important in GDScript as it is in languages that use braces for syntactical structuring, where there can be multiple levels of nested braces spread over 50 lines.