Skip to content
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

Closed
hotelfoxtrotnovember opened this issue Apr 18, 2020 · 4 comments
Closed

shiftup/down does not seem to be working correctly #12

hotelfoxtrotnovember opened this issue Apr 18, 2020 · 4 comments
Labels

Comments

@hotelfoxtrotnovember
Copy link

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:

shiftdown:shift
t
shiftup:shift
e
s
t
shiftdown:shift
1

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:

shiftdown:alt
f

The other shiftup/down commands I tried seemed to have no effect (that is, shift, ctrl, and lwin).

mcec-screenshot


**Snippets from the log**
2020-04-18 15:37:00,726 INFO  - MCE Controller v2.2.3.5 - OS: Microsoft Windows NT 10.0.18363.0 on x64 - .NET: 4.0.30319.42000
2020-04-18 15:37:00,757 INFO  - Settings: Loaded settings from C:\Users\xxx\AppData\Roaming\Kindel Systems\MCE Controller\MCEControl.settings
2020-04-18 15:37:00,945 INFO  - Logger: Logging to C:\Users\xxx\AppData\Roaming\Kindel Systems\MCE Controller\MCEControl.log
2020-04-18 15:37:00,945 INFO  - Telemetry: Disabled
2020-04-18 15:37:00,960 INFO  - Commands: Watching C:\Users\xxx\AppData\Roaming\Kindel Systems\MCE Controller\MCEControl.commands for changes.
2020-04-18 15:37:00,992 INFO  - Commands: 296 built-in commands defined
2020-04-18 15:37:00,992 INFO  - Commands: Loading user-defined commands from C:\Users\xxx\AppData\Roaming\Kindel Systems\MCE Controller\MCEControl.commands
2020-04-18 15:37:01,632 INFO  - Commands: 296 commands loaded
2020-04-18 15:37:01,648 INFO  - Commands: 31 commands enabled (265 commands disabled).
2020-04-18 15:37:01,663 INFO  - Server: Starting...
2020-04-18 15:37:01,663 DEBUG - SocketServer - Binding to IP address: 0.0.0.0:5150
2020-04-18 15:37:01,663 DEBUG - _mainSocket.Listen
2020-04-18 15:37:01,663 INFO  - SocketServer: Started on port 5150
2020-04-18 15:37:01,663 INFO  - SocketServer: Waiting for a client to connect
2020-04-18 15:37:01,476 INFO  - You are running the most recent version of MCE Controller
2020-04-18 15:37:02,925 DEBUG - SocketServer OnClientConnect
2020-04-18 15:37:02,925 DEBUG - Opened Socket #1
2020-04-18 15:37:02,941 INFO  - SocketServer: Client #1 at 127.0.0.1:51235 connected
2020-04-18 15:37:02,941 DEBUG - SocketServer BeginReceive
2020-04-18 15:37:26,622 DEBUG - SocketServer OnClientConnect
2020-04-18 15:37:26,622 DEBUG - Opened Socket #2
2020-04-18 15:37:26,622 INFO  - SocketServer: Client #2 at 192.168.120.69:43158 connected
2020-04-18 15:37:26,622 DEBUG - SocketServer BeginReceive
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: shiftdown:shift
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: t
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: shiftup:shift
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: e
2020-04-18 15:37:45,037 DEBUG - SocketServer BeginReceive
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: s
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: t
2020-04-18 15:37:45,037 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: shiftdown:shift
2020-04-18 15:37:45,037 DEBUG - SocketServer BeginReceive
2020-04-18 15:37:45,178 INFO  - ShiftKey: shift down
2020-04-18 15:37:45,178 INFO  - CharsCommand: Typing 1 chars: t
2020-04-18 15:37:45,193 INFO  - ShiftKey: shift up
2020-04-18 15:37:45,193 INFO  - CharsCommand: Typing 1 chars: e
2020-04-18 15:37:45,193 INFO  - CharsCommand: Typing 1 chars: s
2020-04-18 15:37:45,209 INFO  - CharsCommand: Typing 1 chars: t
2020-04-18 15:37:45,209 INFO  - ShiftKey: shift down
2020-04-18 15:37:49,585 INFO  - SocketServer: Received from Client #2 at 192.168.120.69:43158: 1
2020-04-18 15:37:49,585 DEBUG - SocketServer BeginReceive
2020-04-18 15:37:49,617 INFO  - CharsCommand: Typing 1 chars: 1

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!

@tig
Copy link
Owner

tig commented Apr 18, 2020

Looking at this now... Hang tight.

@tig
Copy link
Owner

tig commented Apr 18, 2020

You can download v2.2.4.607 and this should be fixed. Sorry about that.

@hotelfoxtrotnovember
Copy link
Author

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.

@tig
Copy link
Owner

tig commented Apr 19, 2020

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
Labels
Projects
None yet
Development

No branches or pull requests

2 participants