Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.2
2021.1
2021.2
2021.2.0a5
Issue ID
1315713
Regression
No
The number's precision doesn't change according to the size of the text field to fit the field
How to reproduce it:
1. Open the user's attached project ("New_Unity_Project.zip")
2. Select 'GameObject' in the Hierarchy window
3. Try to shrink and expand the Inspector window
4. Observe 'GameObject' Transform component's fields
Expected result: The displayed numbers in the fields changes according to the field's size. Displayed values fit in the field
Actual result: The displayed numbers in the fields don't change according to the field's size. Displayed values don't fit in the field
Reproducible with: 2018.4.32f1, 2019.4.20f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a5
Comments (1)
-
dpoly
Feb 20, 2021 05:40
In my opinion this is a serious problem for fields displayed in E format (with exponent). The number as displayed appears to lie between 1 and 9, when it actually it may not. This is highly inconvenient, even if you are aware of the possibility. It routinely arises with numbers very close to zero, due to rounding errors.
I agree it is not a problem for values displayed in F format (without exponent). The visible part of the field will show the most significant digits.
I agree truncation is not a good solution. Perhaps you could right justify the number (so the exponent is visible), or highlight it in red (to show the displayed value is misleading), or use F format.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2021.2.X):
After discussions with the UX team truncation based on size is not a desired features we want to implement.