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().
Installing a driver equates a hotplug event on Windows. During the driver installation, you will have disconnection and reconnection of the device. Thus, you're asking for hotplug before we implement hotplug. Well, I could almost agree with you that the lack of hotplug could be considered as a bug that needs fixing, but that applies to libusb(x) as a whole, rather than just the Windows backend. In other words, whatever you want to pretend is a "bug" is actually a missing feature, which belongs to hotplug, and which will naturally be implemented when we add hotplug support to the library. Regards, /Pete ------------------------------------------------------------------------------ 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
