Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.75f1
Issue ID
UUM-142517
Regression
Yes
Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
Steps to reproduce:
- Create a new project
- Select any object with editable numeric fields in the Inspector
- Try changing a value using the arrow controls
- While interacting with the arrow controls, move the pen outside the Inspector window
- Observe the result
Actual Result: The value does not change
Expected Result: The value continues changing as intended
Reproducible with: 2023.2.0a6, 6000.0.75f1, 6000.2.0a5
Not reproducible with: 2023.2.0a5, 6000.3.16f1, 6000.4.8f1, 6000.5.0b9, 6000.6.0a5
Fixed in: 6000.2.0a6
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
-Reproduced with a Wacom tablet and pen
-Also reproduced locally on a touch-screen monitor
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
- AdaptiveLOD sample has missing prefabs and throws missing prefab errors when the AdaptiveLOD sample is imported and the AdaptiveLOD scene is opened
- Error "transform.position assign attempt for 'x' is not valid" is logged when Moving Game Object to View while a Scene is multi selected
- [Desktop] Plastic move detection mixes up identical files
- SVG Icon has tessellation issues in "Antialiased Arc Encodings", ok with "Basic Triangulation"
- "You may not pass null objects" and "Maximized serialized file backup not found" errors are thrown when maximizing and minimizing docked Multiplayer Play Mode window after Multiplayer Play Mode package is uninstalled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.