On 2012.05.14 19:41, Peter Stuge wrote: > Pete Batard wrote: >> Right now, outside of not freeing the list (but in that case, expecting >> an enum list to auto-update itself if after it has been generated IS >> hotplug), > > You seem to miss that the list is expected to be updated on call to > libusb_get_device_list() - noone has said anything about auto-updating.
And noone has said anything about the Windows backend being feature-complete before hotplug is done. Actually, if you look at the Wiki, you'll see that the Windows backend is still very much flagged as experimental [1]. This is not a mistake. Again, why bother implementing part of something early, when the same is likely to be provided in a different manner, when a complete feature is implemented. Unless the expectation is that a lot of people will be affected before the full implementation is done, which I don't currently see (it took a custom implementation of the actual feature we plan to duplicate to raise the prospect of an issue here), and one values their time, it makes a lot of sense to wait for the full feature implementation. Regards, /Pete [1] http://sourceforge.net/apps/mediawiki/libusbx/index.php?title=Main_Page#Supported_Environments ------------------------------------------------------------------------------ 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
