You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support using multiple keyboard and other HID devices independently from each other.
The input API already has a keyboard index API but at least on Windows it's always zero. The raw keyboard API provides ways to get various information about the source device for a Windows keypress event. This includes enough information to have a non-zero index value as well as vendor+product id so it's possible to identify exactly what device it is.
I don't know how to do this in other operating systems but it should be possible. I would like to avoid adding something platform dependent in my application which is why I suggest this as a feature in SILK, hiding away the specific platform API for doing this.
Note that the online examples for using the windows raw keyboard API from C# doesn't pin the struct between registering and unregistering for raw keyboard notifications. This randomly makes the application stop receiving raw keyboard notifications which is rather annoying. Also not unregistering properly leads to a kernel memory leak like many other Windows API:s so don't do that.
The text was updated successfully, but these errors were encountered:
Support using multiple keyboard and other HID devices independently from each other.
The input API already has a keyboard index API but at least on Windows it's always zero. The raw keyboard API provides ways to get various information about the source device for a Windows keypress event. This includes enough information to have a non-zero index value as well as vendor+product id so it's possible to identify exactly what device it is.
I don't know how to do this in other operating systems but it should be possible. I would like to avoid adding something platform dependent in my application which is why I suggest this as a feature in SILK, hiding away the specific platform API for doing this.
Note that the online examples for using the windows raw keyboard API from C# doesn't pin the struct between registering and unregistering for raw keyboard notifications. This randomly makes the application stop receiving raw keyboard notifications which is rather annoying. Also not unregistering properly leads to a kernel memory leak like many other Windows API:s so don't do that.
The text was updated successfully, but these errors were encountered: