Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a10
Issue ID
1105417
Regression
Yes
Using range serialized field will not update the inspector correctly.
Steps to reproduce
- Open the attached project in 2018.3.0f1
- Select the cube object
- Open the script CubeMovement
- Change [Range(0f, 100f)] to [Range(10f, 100f)]
- Select the cube object again
Notice issue >> The knob for the range slider disappears. The value box is set to zero. It won't display correctly until you click on the slider.
Expected
The range value should update to 10 and the knob for the slider should appear.
Tested: 2018.2.1, 2018.3.0b8, 2018.3.0f1, 2019.1.0a10
Working: 2018.2.1
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
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Resolution Note (2019.1.X):
I'm looking at the bug, and I believe the behaviour is by design.
- Original range is between 0-100
- Users sets value to 0
- Range changes to 10-100
- 0 is now outside the range.
we do not show the knob when values are outside the range, and we do not change values without an explicit user interaction. The Range attribute is an UI attribute, not an enforcement, if an object needs to enforce a range, it should do that enforcement in their OnValidate callback.
In the version marked as working, the value is not updated either. However the slider knob is visible. this is because a validation check is missing in the painting of the slider
Resolving this case as by design