fikovnik / ShiftIt

Managing windows size and position in OSX
5.54k stars 360 forks source link

macOS Ventura 13.3 – no hotkeys after focus shift by keyboard #335

Closed Baloobear closed 1 year ago

Baloobear commented 1 year ago

Since my update from 13.2 to 13.3 of macOS Ventura I face the problem that the hotkeys stop working when I shift the focus to another application with CMD + Tab. Staying within the application (e.g. Chrome Browser) works in the beginning but stops working after a while, too.

After switching to another application, e.g. by mouse click to another window, the hotkeys only work in some cases, but in an unpredictably manner.

The debug log prints out the following lines after trying to max/min/switch screen:

2023-04-05 13:20:00.341 ShiftIt[701/0x7ff848d37340] [lvl=3] -[ShiftItAppDelegate invokeShiftItActionByIdentifier_:] Execution of ShiftIt action: maximize failed: Unable to get active window
NSError stack trace:
org.shiftitapp.shifit.error:20103 - Unable to get active window
  Caused-by: org.shiftitapp.shifit.error:20101 - Unable to find focused window owner
2023-04-05 13:21:34.809 ShiftIt[701/0x7ff848d37340] [lvl=3] -[ShiftItAppDelegate invokeShiftItActionByIdentifier_:] Execution of ShiftIt action: reduce failed: Unable to get active window
NSError stack trace:
org.shiftitapp.shifit.error:20103 - Unable to get active window
  Caused-by: org.shiftitapp.shifit.error:20101 - Unable to find focused window owner
2023-04-05 13:21:47.881 ShiftIt[701/0x7ff848d37340] [lvl=3] -[ShiftItAppDelegate invokeShiftItActionByIdentifier_:] Execution of ShiftIt action: nextscreen failed: Unable to get active window
NSError stack trace:
org.shiftitapp.shifit.error:20103 - Unable to get active window
  Caused-by: org.shiftitapp.shifit.error:20101 - Unable to find focused window owner

Is there any more information needed, please let me know.

eduardoroliveira commented 1 year ago

Try restarting your Mac. It solved my problem!

Baloobear commented 1 year ago

Strange, since I tried a reboot already which haven't fixed the issue my last reboot seemed to fix the problem.

Okay, maybe just some awkward behavior. Thanks for the hint.