We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running the notification example cargo run --example notification --features=unstable_xtarget_notification I've observed the following behavior:
cargo run --example notification --features=unstable_xtarget_notification
xinput.set_state
Maybe related is this commit which uses multiple concurrent XUsbRequestNotification requests however it was dealing with missed notifications due to too many being sent: https://gist.github.com/Ryochan7/f41bd345c5592d88f37ff24773e1e882
Related issue: Ryochan7/DS4Windows#1730
I don't expect these issues to be resolved any time soon.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When running the notification example
cargo run --example notification --features=unstable_xtarget_notification
I've observed the following behavior:xinput.set_state
calls.Maybe related is this commit which uses multiple concurrent XUsbRequestNotification requests however it was dealing with missed notifications due to too many being sent: https://gist.github.com/Ryochan7/f41bd345c5592d88f37ff24773e1e882
Related issue: Ryochan7/DS4Windows#1730
I don't expect these issues to be resolved any time soon.
The text was updated successfully, but these errors were encountered: