Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
1073162
Regression
No
[OSX Editor] During Playmode, the cursor does not unlock for several windows called out through shortcut.
If the project has cursor lock during play, the user cannot regain control after calling out a window during Playmode.
This happens to windows that are external to Unity. For example, if user call out Build Setting window, which is a native Unity Editor window, the cursor unlocks and everything works well. If user chooses CMD + B (Build...), and a Mac system window shows up, asking for save location and file name, the cursor remains locked.
List of the same situations during Playmode:
- Build (CMD + B)
- Open (CMD + O)
- Calls out Mission Control (Three finger swipe up. See attached image for reference)
Repro:
1. Launch Unity and open the attached project
2. Open "Main" scene
3. Enter Playmode (make sure the cursor is locked in the game view)
4. Press CMD + B or any action from the list above
5. Try to use mouse and move the cursor.
Expected: Cursor is free to move when a window pops out in Playmode
Actual: Cursor does not unlock when a window shows up in Playmode
Similar bug: https://fogbugz.unity3d.com/f/cases/1006813/
And it is fixed in PR: https://ono.unity3d.com/unity/unity/pull-request/72586/_/platform/osx/fix-cursor-locked-on-exit
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.2.X):
This seems to be fairly uncommon scenario, does not meet the priority bar at the moment