Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.4f1
Issue ID
UUM-72742
Regression
No
[WinARM] Scene Overlays can't be docked using touch screen controls
Steps to reproduce:
1. Create a new project
2. Open the Scene view window
3. Try moving one of the Overlays and docking it
Actual results: The Overlay handle is moved highlights for docking appear. However, the Overlay gets either stuck onscreen or does not dock when placed over a highlighted spot and returns to the original after interacting with a different window
Expected results: The Overlay can be moved and docked the same way as when using mouse controls
Reproducible with versions: 2023.3.0a3, 6000.0.4f1
Can’t test with versions: 2021.3.39f1, 2022.3.31f1, 2023.2.20f1 (Windows ARM was not yet supported
Tested on (OS): Windows 11 ARM
{}Tested on (Device){}: MS Surface PRO 9
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue now, as we are committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue now, as we are committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.