New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 10 Erratic Performance #16

Closed
sheldonhull opened this Issue Aug 24, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@sheldonhull

sheldonhull commented Aug 24, 2016

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.

@sheldonhull

This comment has been minimized.

Show comment
Hide comment
@sheldonhull

sheldonhull Oct 31, 2017

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

sheldonhull commented Oct 31, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment