Change Details

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59 **Blender Version** Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-08-22 16:16, hash: `rB7f6cd405b99c` **Short description of error** I often encountered while working on Windows, that from time to time the `Ctrl` key would get locked (always held) even though I am not pressing it. Repeatedly pressing and releasing the key would fix the issue. Finally I found a way to reproduce the issue for me. I organise open windows into separate Desktops that I switch between regularly. Whenever I switch between them, if Blender was the active window at the time, the `Ctrl` key would get stuck. This is likely the case because the shortcut to switch Desktops is `Ctrl + Windows Key + Left/Right Arrow`. I think this issue is specific to Blender and not just Windows 10, because other programs do not have this issue. **Exact steps for others to reproduce the error** - Create a second Desktop on Windows 10 - Open Blender on the first Desktop - Use `Ctrl + Windows Key + Right Arrow` to switch to the other Desktop - Switch back with `Ctrl + Windows Key + Left Arrow` - Use the middle mouse button to pan in the viewport Instead of panning it will zoom in the viewport instead.

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59 **Blender Version** Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-08-22 16:16, hash: `rB7f6cd405b99c` Worked: version 3.3 Beta **Short description of error** I often encountered while working on Windows, that from time to time the `Ctrl` key would get locked (always held) even though I am not pressing it. Repeatedly pressing and releasing the key would fix the issue. Finally I found a way to reproduce the issue for me. I organise open windows into separate Desktops that I switch between regularly. Whenever I switch between them, if Blender was the active window at the time, the `Ctrl` key would get stuck. This is likely the case because the shortcut to switch Desktops is `Ctrl + Windows Key + Left/Right Arrow`. I think this issue is specific to Blender and not just Windows 10, because other programs do not have this issue. **Exact steps for others to reproduce the error** - Create a second Desktop on Windows 10 - Open Blender on the first Desktop - Use `Ctrl + Windows Key + Right Arrow` to switch to the other Desktop - Switch back with `Ctrl + Windows Key + Left Arrow` - Use the middle mouse button to pan in the viewport Instead of panning it will zoom in the viewport instead.

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59 **Blender Version** Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-08-22 16:16, hash: `rB7f6cd405b99c` Worked: version 3.3 Beta **Short description of error** I often encountered while working on Windows, that from time to time the `Ctrl` key would get locked (always held) even though I am not pressing it. Repeatedly pressing and releasing the key would fix the issue. Finally I found a way to reproduce the issue for me. I organise open windows into separate Desktops that I switch between regularly. Whenever I switch between them, if Blender was the active window at the time, the `Ctrl` key would get stuck. This is likely the case because the shortcut to switch Desktops is `Ctrl + Windows Key + Left/Right Arrow`. I think this issue is specific to Blender and not just Windows 10, because other programs do not have this issue. **Exact steps for others to reproduce the error** - Create a second Desktop on Windows 10 - Open Blender on the first Desktop - Use `Ctrl + Windows Key + Right Arrow` to switch to the other Desktop - Switch back with `Ctrl + Windows Key + Left Arrow` - Use the middle mouse button to pan in the viewport Instead of panning it will zoom in the viewport instead.