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

key is captured, but still sent through anyway #49

Open
wkearney99 opened this issue Feb 11, 2023 · 2 comments
Open

key is captured, but still sent through anyway #49

wkearney99 opened this issue Feb 11, 2023 · 2 comments

Comments

@wkearney99
Copy link

I'm hoping to use a Chatpad keyboard connected to a wired Microsoft Xbox controller. This is an original Xbox Chatpad, not one of the aftermarket knock-offs. It uses the same connection as the Xbox controller, not a separate USB receiver. It does show up in Windows as a HID device.

The quickstart script sees the keyboard and does detect the CHN sample keystrokes. But the same CHN keys still get sent through to whatever the active text entry screen is at the moment.

I can press c here in this box, calc.exe is started, but the letter c is still also entered here into this text box.

Is there a way to suppress that follow-on keystroke?

I have tried this with another 'regular' USB keyboard and that one DOES NOT have the pass-through problem.

I think I have figured out part of the problem. If I have the Steam game client running I get the problem. If I quit the Steam client the problem goes away. This is not a solution, however, as the whole point of my attempt here is to use the macros during gameplay and that requires the Steam client.

I'm "guessing" the steam client is using some of the same tricks as luamacros to capture and manage the inputs through the controller and chatpad?

@wkearney99
Copy link
Author

I posted about it on the forum: http://hidmacros.eu/forum/viewtopic.php?f=10&t=4344&p=6620#p6620

I think this may be the issue: http://hidmacros.eu/forum/viewtopic.php?f=10&t=4344&p=6620#p6620

I don't know if the Steam client can be configured to work around this or not.

@wkearney99
Copy link
Author

I can confirm that another Xbox chatpad alternative that uses it's own USB wireless receiver does not have the same double-entry issue as the factory original Microsoft Chatpad. Which makes sense, as it's not really connecting 'through' the Xbox controller's USB connection (and thus not through it's driver subsystem). So the Steam game client doesn't pay any different attention to it, as it thinks it's just another keyboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant