You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2D game, I sometimes use rects (like rect region or something)
Describe the problem or limitation you are having in your project
So after the most recent inspector makeover the inspector was optimized to have more space etc. But then there are Rect2 properties, that feel really cramped. I mean, the input fields have only space for few digits. It's ok when you edit them because they expand, but when you look over these properties, you can't immediately tell the exact value.
This illustrates the problem really well:
Describe the feature / enhancement and how it helps to overcome the problem or limitation
It would be better if rect property field had 2 rows. One for x/y and one for w/h. It might take more vertical space, but it would be more readable.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
The relevant code is in editor_properties_array_dict.cpp.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not really, no.
Is there a reason why this should be core and not an add-on in the asset library?
That would require a custom inspector as an add-on.
The text was updated successfully, but these errors were encountered:
So I just discovered that there's an editor setting horizontal_vector_types_editing that affects few types.
Still, 2x2 would be more optimal layout IMO.
Describe the project you are working on
2D game, I sometimes use rects (like rect region or something)
Describe the problem or limitation you are having in your project
So after the most recent inspector makeover the inspector was optimized to have more space etc. But then there are Rect2 properties, that feel really cramped. I mean, the input fields have only space for few digits. It's ok when you edit them because they expand, but when you look over these properties, you can't immediately tell the exact value.
This illustrates the problem really well:
Describe the feature / enhancement and how it helps to overcome the problem or limitation
It would be better if rect property field had 2 rows. One for x/y and one for w/h. It might take more vertical space, but it would be more readable.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
The relevant code is in
editor_properties_array_dict.cpp
.If this enhancement will not be used often, can it be worked around with a few lines of script?
Not really, no.
Is there a reason why this should be core and not an add-on in the asset library?
That would require a custom inspector as an add-on.
The text was updated successfully, but these errors were encountered: