-
Notifications
You must be signed in to change notification settings - Fork 8
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
Hook on Linux x11 non-responsive #22
Comments
Hi, |
Must investigate how the game actually gets its events, but spamming the game with events makes the overlay receive events. I guess the game use something else than XEventsQueued or XPending to get its events. |
I'm on kde5, pure x11 session on Arch Linux
@_@ |
Mystery solved, this game doesn't use libX11, it uses libxcb:
I need a new driver for libxcb alongside libX11: #23 Anyway, developpers should stop doing strange stuff. Why would you use both libX11 AND libxcb for your X server events ? |
Found a new game that influenced by this issue and have exactly same behavior, Factorio. |
I agree the fact that using both libraries is valid, but what is incorrect is to use both libraries to get the X server events. That makes conflicts like in Stellaris when the X event queue gets clogged, both xcb and libX return events |
Tested the new commit, it give me this error |
The xcb hook branch is absolutely not ready. I didn't encounter any of your issue, this is surely because you didn't link the correct xcb libraries. Right now the issue is that I don't know how to get the same behavior with xcb as X11 hooks, it always hangs. |
This is similar to #6, hooks to the game Stellaris.
I added the line
to line 267 of X11Hook.cpp, launch game and keeps typing the key combination whole time, get the result:
When the game just launched, I can get the normal 2 (KeyPress), 3 (KeyRelease) and 6 (MotionNotify) event and open overlay, then it changes to these unknown 85 events and key press not respond anymore.
https://github.com/otavepto/gbe_fork/issues/20#issuecomment-2028833242
The text was updated successfully, but these errors were encountered: