Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3
2019.3.10f1
2020.2
Issue ID
1244514
Regression
No
[UIElements] FloatField.formatString is not applied to initial field values
Reproduction steps:
1. Open attached project "FieldFormat"
2. In Menu bar, open Window -> UIElements -> Test
3. In Test window, observe "field1" format
Expected result: The field has a decimal point
Actual result: The field does not have a decimal point
Reproducible with: 2019.3.13f1, 2020.1.0b8, 2020.2.0a11
Could not test with: 2018.4.22f1 (UIElements namespace does not exist)
Notes:
1. The proper field format is applied upon field value update, or after selecting and deselecting the field
2. Updating the field value on initialization fixes the issue.
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
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a16