On second thought, looking at the `HRESULT_FROM_SETUPAPI` macro, I think we can
probably avoid creating a new function call, by simply applying
`HRESULT_FROM_SETUPAPI` in `windows_error_str()` when it's not able to
translate the message. Will try to work something out in that direction.
/Pete
The overall opinion seems to be that we don't want to merge this proposal for
the time being. I will therefore close the issue.
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/156#issuecomment-31307212--
Closed #156.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/156--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear pi
Closed #137.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/137--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear pi
I still don't think this is a satisfactory proposition, and I don't believe we
want something that removes functionality just to work around a bug that, by
all means, should not be libusb's to fix.
I am therefore going to close the request. If someone needs that kind of
workaround, they can alw
Closed #157 via 28424b945cc5abed182f83ab3fc70676986d7cf3.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/157--
Rapidly troubleshoot problems before they affect your business.
Closed #154 via 7e3de5de095a493accc77081fb384be8e9144250.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/154--
Rapidly troubleshoot problems before they affect your business.
Closed #134 via 650e22508f6d595d73d565423cb06b14049bd3af.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/134--
Rapidly troubleshoot problems before they affect your business.
Hi Matthias,
Thank you for the reply.
Am 23.12.2013 12:15, schrieb Matthias Bolte:
>
> I think there could be two reasons for this problem:
>
> 1) There is a bug in libusbx, your specific usage pattern triggers it
> and in the end your transfer is lost. Are you using the latest
> release/git vers
