Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.39f1
2021.3.9f1
2022.1.15f1
2022.2.0b6
2023.1.0a9
2023.2.0a1
Issue ID
UUM-13128
Regression
No
UI Slider does not recognize Touch Input when attempting to drag on Windows 7
How to reproduce:
1. Open the user-attached project
2. Build and Run the project (File → Build and Run)
3. Attempt to drag the Slider Widget in the Build with Touch Input
Expected result: The Slider follows the drag Touch Input
Actual result: The Slider moves only on Double-Click/Double-Tap Touch Input
Reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b6, 2023.1.0a9
Reproduced on: Windows 7_x64 and DELL P2418HT Touch Screen Monitor
Note:
- When opening the Editor with any project Touch Input no longer works (Reported IN-14891)
- Before testing first create builds then restart your system so that Touch Input would work again
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:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.