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

Keys not working #2

Closed
thaboy1992 opened this issue Apr 26, 2020 · 5 comments
Closed

Keys not working #2

thaboy1992 opened this issue Apr 26, 2020 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@thaboy1992
Copy link

Hi,

Software installed: Yes and working
Hardware installed: Yes and LCD keys are getting data from the software so thats okay.

The only issue i have is, when i press a LCD button, nothing happens.

Did you had the same problem?

OS: Win 7 64-bit

@atom0s
Copy link
Owner

atom0s commented Apr 27, 2020

Hello guys, thanks for the report. I am looking into this currently.

For Windows 7 there appears to be a failure while calling one of the service level APIs, in this case:

  • WTSGetActiveConsoleSessionId
  • WTSQuerySessionInformationW

The StreamDeck software is checking the current session information with the 'WTSSessionInfoEx' flag here for some reason and this is landing up returning bad data causing the function using it to return a bad value. This return causes the StreamDeck to skip over processing the grid key press. (Pressing a button on the deck.)

I am not familiar with this API so I am looking into this a bit more before I opt. to just patch the given function as needed to bypass this check. But, I am able to make the deck fully work on Windows 7 by adjusting the program to ignore what this API is doing. So I will hopefully have something posted in the near future to fix this for Windows 7.

@atom0s atom0s self-assigned this Apr 27, 2020
@atom0s atom0s added the bug Something isn't working label Apr 27, 2020
@thaboy1992
Copy link
Author

thaboy1992 commented Apr 27, 2020 via email

@atom0s
Copy link
Owner

atom0s commented Apr 27, 2020

If any other developer runs into this issue, it appears this is a known bug to Microsoft, yay..

Windows Server 2008 R2 and Windows 7: Due to a code defect, the usage of the WTS_SESSIONSTATE_LOCK and WTS_SESSIONSTATE_UNLOCK flags is reversed. That is, WTS_SESSIONSTATE_LOCK indicates that the session is unlocked, and WTS_SESSIONSTATE_UNLOCK indicates the session is locked.

@thaboy1992
Copy link
Author

thaboy1992 commented Apr 27, 2020 via email

@atom0s
Copy link
Owner

atom0s commented Apr 27, 2020

This is now fixed in the latest release. :) v1.0.0.1
https://github.com/atom0s/ElgatoLegacy/releases/latest

@atom0s atom0s closed this as completed Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants