Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
10
Found in
2018.1.0a1
2018.1.0f2
Issue ID
1047005
Regression
Yes
Cursor.lockState is ignored after Alt+Tab
Reproduction steps:
1. Open the attached project "CursorSample_Project";
2. Build the project for MacOS or Windows;
3. Open the built project;
4. Alt+Tab (Command + Alt) to another window and then Alt+Tab back to the build.
Expected results: the cursor is still locked in the point it was locked before losing focus on the built project window.
Actual results: the cursor acts just as Cursor.lockState would be set to None.
Reproduced on: 2018.1.0a1, 2018.1.5f1, 2018.2.0b9, 2018.3.0a2.
Not reproduced on: 2017.3.2f1, 2017.4.5f1.
Reproduced both on MacOS and Windows
Workaround: check the "Run in background" option in the Player settings.
Fixed in 2018.3
Comments (2)
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
- Incorrect error box style when installing the unsigned package in the Package Manager's "Invalid Signature" pop-up
- "Invalid Signature" pop-up incorrectly wraps the text when using the Light theme
- WebGPU: can't bind compute RWTexture for read and write
- WebGPU: errors with unorm and half4 RWTexture
- Error indicating that Importer has not been disposed properly is logged when switching to or from the Texture Importer type in a Focused Inspector
martin-sustek
Jul 23, 2018 17:50
Even with the “Run in background” enabled, the behavior is different than before - after switching back, the cursor is on different monitor (multi-monitor setup) and you need to click back into the window.