Closed sheldonhull closed 6 years ago
I think one of the issues is elevated permissions. When I ran AHK script without elevation, elevated aps couldn't receive the command. Once I ran AHK script as admin, the issue went away.
I just replicated this behavior by running VSCODE as admin, and AHK as nonadmin. Failed to move window. Restarted VSCODE as admin and WindowPadX as admin, and then it worked successfully.
Darn permissions issues in windows! Always will get you
Initially WindowpadX on windows 10 was working, but my more recent usage is not working consistently. Not sure what exactly to check, but the shortcut-keys for windows numberpad are not staying bound to the autohotkey script. Reloading the WIndowPadX.ahk script doesn't fix the issue either.
Not sure if Windows 10 has any changes for binding keys that I could look into.
Any suggestions welcome, as I'd like to get WindowPadX back to working. Has been the best longterm performing solution I've used.