Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2
2019.2.2f1
2019.3
2020.1
Issue ID
1196013
Regression
No
UIElements Range does not work when field is set to float
How to reproduce:
1. Open attached project ("RangeBug.zip")
2. Open SampleScene scene
3. Select TestObj Game object
4. Open Inspector window
5. In Test Component change Value field to anything outside [0;10] range
Expected result: Value in Value field is constrained by [0;10] range
Actual result: Value in Value field is not constrained by [0;10] range
Reproducible with: 2019.2.12f1, 2019.3.0b10, 2020.1.0a12
Not reproducible with: 2017.4.34f1, 2018.4.12f1 (CreateInspectorGUI can not be overridden)
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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Resolution Note (2020.1.X):
The reason for the described behavior is because the binding system subscribed to the same ValueChangedCallback. There is no mechanism that would allow us to make sure the binding system will get ValueChangedCallback before the user code.
To achieve the correct result, use the OnValidate function.
https://docs.unity3d.com/ScriptReference/MonoBehaviour.OnValidate.html