Search Issue Tracker
Third Party Issue
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.2
2021.2.0b4
2022.1
Issue ID
1353992
Regression
No
Prefab doesn't detect overrides when changing MinMaxSlider values in the Prefab instance
How to reproduce:
1. Open the user's attached "GizmoBug.zip"
2. Open the "SampleScene" Scene
3. Select the "Test" GameObject in the Hierarchy
4. Drag the "Test Min Max" property's slider in the Inspector
5. Observe the "Test Min Max" property
Expected result: Changing MinMaxSlider values adds an override to the Prefab
Actual result: Changing MinMaxSlider values doesn't add an override to the Prefab
Reproducible with: 2018.4.26f1, 2019.4.29f1, 2020.3.15f1, 2021.1.17f1, 2021.2.0b5, 2022.1.0a4
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Hi, as the code MinMaxSlider is not an official Unity code, but from a third party GitHub project, we cannot help resolving the issue in the code.
However when looking at the MinMaxSliderDrawer code it attempts to care of all the responsibilities a property drawer has, however it doesn't implement all the features you request such as the blue property override line. Your simplified version works because it directly calls the official property drawers that do implement the requested features.