I kind of like that HIDSharp doesn't prevent multiple streams. I have found that I can shave about 7-8ms off of an HID communication by leaving streams open , or only opening them once for multiple transactions. Sometimes I run into situations where it would be convenient to know if a particular HID has an open stream. I try to limit to one stream per HID, but the code gets fairly complex when I have to send large operations off into a background worker thread, while still allowing the user to manipulate unit's internal params via the UI. Currently thinking of rewriting the app I have now and I was just curious.
It is an app that controls any number of little HID devices, all the same VID/PID and all pretty much identical.
When my app discovers a unit being attached, do you think it is OK to open a stream and leave it open for the duration of that unit's interaction with the app?
What did you mean about _have_ to do this with Windows 10?
Thank you for your reply!