You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After merging the development branch into my local copy, I started getting an occasional Access Denied error on startup, which I traced to this line in actions2.py failing:
After a little googling, it appears that SPI_SETFOREGROUNDLOCKTIMEOUT will fail if any of the conditions are not true:
The process is the foreground process.
The process was started by the foreground process.
The process received the last input event.
There is no foreground process.
The foreground process is being debugged.
The foreground is not locked (see LockSetForegroundWindow).
The foreground lock time-out has expired (see SPI_GETFOREGROUNDLOCKTIMEOUT in SystemParametersInfo).
No menus are active.
It doesn't happen all the time, and I can't identify a pattern to it yet. I'm also not sure what the purpose of that line is or what the impact to the rest of actions2.py is if it fails. For now, I've wrapped it in a try/except so that it won't break the whole start up process.
That is t4ngo's suggested solution to the 64-bit focus window executable problem (which Daanzu fixed). It is no longer necessary and has been commented out in the most recent commit.
After merging the development branch into my local copy, I started getting an occasional Access Denied error on startup, which I traced to this line in actions2.py failing:
After a little googling, it appears that
SPI_SETFOREGROUNDLOCKTIMEOUT
will fail if any of the conditions are not true:It doesn't happen all the time, and I can't identify a pattern to it yet. I'm also not sure what the purpose of that line is or what the impact to the rest of actions2.py is if it fails. For now, I've wrapped it in a try/except so that it won't break the whole start up process.
The text was updated successfully, but these errors were encountered: