Ihor Dutchak

Windows and macOS is fine. Libusb and Hidraw - I see multuple improvements to perform before it is ready as far as I can tell. @Julusian do you feel comfortable...

Updated the implementation to have lazy initialisation for libusb backend. During the refactoring, found a bug: `hidapi_initialize_device` hasn't been filling up the `device_info->interface_number` field. With new implementation such kind of...

Another libusb update: sorted out the "get usage_page/usage". It has to be handled differently during the enumeration and when the device is fully opened.

Now I'm happy with libusb implementation.

Since no one complains about my latest changes - either everything works as expecter or no one had a chance to look :)

> The libusb backend will detach the hidraw driver so that hidraw backend will not be able to find the device. That is actually unexpected. LIBUSB backed should have re-attach...

> Let me check. As far as I can tell - the driver _was_ reattached (otherwise you wouldn't be able to enumerate it with hidraw after libusb). Maybe there is...

There is an interesting side-effect/improvement in libusb backed: Before this change, the only way to get (primary) usage_page/usage was to compile hidapi with `INVASIVE_GET_USAGE`. Now - it is possible to...

On each OS the artifact name is different (.dll/.so/.dylib) so with single matrix for different OS-s we'd have a bunch of `if`s or an andditional variable, which I don't find...

> our current use of HIDAPI has separate threads for reading and writing with the reading thread using hid_read_timeout with a 500ms timeout I believe that's the only way HIDAPI...