Pete Batard wrote: > On 2012.05.14 18:44, Peter Stuge wrote: > > I don't think that should be neccessary. If replacing the driver does > > not lead to a new libusb_device * for the device then I think it is a > > bug if the device must be destroyed before accurate state is reported > > by calls to _get_device_list(). > > .. hotplug ..
The bug is that the Windows backend requires a libusb_device * to be unref:ed before libusb_get_device_list() reports system changes, while other backends do not have this limitation and it is documented that libusb_get_device_list() does not have this limitation. > you're asking for hotplug before we implement hotplug. No, I'm confirming that the non-hotplug-supporting API has a bug in the Windows backend. > whatever you want to pretend is a "bug" is actually a missing feature, I just confirmed that it's a bug. The bug was obviously reported by Uri together with his patch, and then further explained by Hans. //Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
