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
Describe the problem or limitation you are having in your project
When a Control's size is determined by its Container, the editor now hides the size because it shouldn't be editable. However, oftentimes it's necessary to know what the size is, and now the only way to determine it is via running the game and debugging (which can crash the program in C#) or printing to the console (tedious).
Describe the feature / enhancement and how it helps to overcome the problem or limitation
The size for Controls that are inside Containers should be exposed as an un-editable field.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Same as it is in 3.x, but not editable.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Yes, but it's tedious or crash-y for how often it's needed.
Is there a reason why this should be core and not an add-on in the asset library?
This is a modification to a core feature.
The text was updated successfully, but these errors were encountered:
I am for making it optional, and maybe hidden by default, but also allow to see controls position, and maybe even rotation - for example for those who animates buttons inside containers
Describe the project you are working on
A 2D game with menus
Describe the problem or limitation you are having in your project
When a
Control
's size is determined by itsContainer
, the editor now hides the size because it shouldn't be editable. However, oftentimes it's necessary to know what the size is, and now the only way to determine it is via running the game and debugging (which can crash the program in C#) or printing to the console (tedious).Describe the feature / enhancement and how it helps to overcome the problem or limitation
The size for
Control
s that are insideContainer
s should be exposed as an un-editable field.Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Same as it is in 3.x, but not editable.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Yes, but it's tedious or crash-y for how often it's needed.
Is there a reason why this should be core and not an add-on in the asset library?
This is a modification to a core feature.
The text was updated successfully, but these errors were encountered: