Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4
2018.4
2019.4
2020.1
2020.2
2020.2.0a15
Issue ID
1256909
Regression
No
Double clicking on non-equal values and trying to type over them results in "<>" symbols added to the field
How to reproduce:
1. Open the attached project
2. Select the two "Array" objects in the "SampleScene"
3. Observe that the array values are non-equal for the two objects and thus show the "-' symbol
4. Either double click the value - type in a new one or slightly drag over the existing "-" value and then type in a new one
5. Observe the value that actually shows up
Expected result: If you double click on a value to select it and then type in "5" for example then 5 should be the new value
Actual result: If you double click on a value to select it and then type in "5" the value ends up as "<5>" which resets it to 0. A similar thing happens when you drag your mouse slightly over the value's text - it ends up as "<mul5>", "<m5>", etc.
Reproduced in: 2020.2.0a15, 2020.1.0b14, 2019.4.2f1, 2018.4.23f1, 2017.4.40f1
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b1