Remove the gray outlines around active tree elements #9123
Replies: 3 comments 1 reply
-
I agree with removing this outline, and also making the select highlight cover the entire line. Right now, it doesn't span the entire line in the Scene tree dock but it does in the signals dock you shown. |
Beta Was this translation helpful? Give feedback.
-
Just quoting what I said on Twitter to @passivestar: keep all the outlines toggeable with "Draw Extra Borders", it's very important for visual accessibility and readability, just like most popular IDEs' "high contrast" themes. And to keep things consistent, all outlines should come disabled by default and appear only if "Draw Extra Borders" is on? In any case, even "Draw Extra Borders" is currently inconsistent - where are the outlines here, for example? |
Beta Was this translation helpful? Give feedback.
-
The cursor box is still there because the tree is in multiple select mode. There is no box on Tree controls that are configured in Single or Row select modes. Any Tree can already have its whole row be highlighted - it is sufficient to put it in Row selection mode. But this is not compatible with multiple selection mode yet - something that can be developed! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The gray outline around the tree active element is called a "cursor"
Since godotengine/godot#86218 was merged in december it's no longer possible to see that cursor separately from the selected item (to my knowledge), because the arrow keys now change the actual selection and not just the cursor
Now that that's the case, the gray outline is no longer necessary and can be removed for less visual noise and for consistency with the look of active elements in the other parts of the editor's UI, as a lot of them don't have that gray outline:
In the short-term this can be done by just swapping out the style for the cursor to an empty stylebox
In the long-term perhaps the concept of the cursor itself could be revisited. I don't know the internals of Godot well enough to go as far as saying that the cursor needs to be removed altogether from the codebase, but at least as a user of the engine I can say that it feels like it doesn't really contribute anything to the UX
Beta Was this translation helpful? Give feedback.
All reactions