-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
shiftup/down does not seem to be working correctly #12
Labels
Comments
Looking at this now... Hang tight. |
tig
added a commit
that referenced
this issue
Apr 18, 2020
You can download v2.2.4.607 and this should be fixed. Sorry about that. |
No worries, thanks for the fast turnaround! Love this project, thanks so much for doing it and keeping it up to date! I can confirm that the fix appears to have corrected the issues I observed. |
I just pushed a minor fix with 2.2.4.621. If auto-update detection doesn't see it, please update manually. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In version 2.2.3.5, it seems like the shiftup/down commands are not working properly/are being ignored. I recently upgraded from a fairly old version (1.8, I think) to the latest version and noticed the changed behavior. To be clear, I did enable "chars:" and "shiftup:" and "shiftdown:" commands.
To Reproduce
Just using the documentation as an example, to type the string "Test!" by sending these commands:
The output I get is "test1". (see attached screenshot) I've also experimented with other combinations with similar results. shiftdown:alt and shiftup:alt do seem like they may behave correctly at least some of the time. For example, when notepad was in the foreground, this sequence brought up the file menu as expected:
The other shiftup/down commands I tried seemed to have no effect (that is, shift, ctrl, and lwin).
Desktop (please complete the following information):
I'm trying to interface from Home Remote, but the above testing was done via PuTTY, with no difference in behavior.
Happy to provide any other info that might be useful in tracking this down.
Thanks!
The text was updated successfully, but these errors were encountered: