Hi Jan, On 2013.08.13 16:15, Jan Becvar wrote: > Forgot to add that my idea/hope was that libusbx, when setting backend > of a composite interface, could check if this is not by chance first > interface of an IAD-collection and if so, assign the same backend to the > other interfaces of the collection as well. But I don't know in the > moment, if such approach wouldn't interfere with the general design of > libusbx or with one of the libusbx-supported drivers.
It's more a case of this is a problem that very few people are expected to encounter without being able to use either the workaround of replacing the composite parent driver or have their app figure out which interfaces are accessible from libusb and which aren't, so we're not going to invest much resources into solving it (too few developers, too little time). If it's of interest to you, eventually, we are planning to provide an interface that will allow Windows users to gain access to Windows specific data, such as the name of the driver being used to access a device/interface and/or whether it is libusb compatible. The idea then would be that you would use that information in your app to decide which interfaces are accessible. Unless we get many requests to add logic to allow additional interface access based on the driver, we'll leave libusb users add that logic in their application instead. As you will understand, adding complexity in the library for uncommon situations that can be handled at the app level is something we'd prefer to avoid. The reason is it introduces points of failure that then need to be tested forever and, unlike other software, automating the testing of a library that relies on the presence of external hardware devices isn't a problem that has a quick and easy solution. Microsoft decided to present devices with multiple interfaces as independent devices on Windows by default, so if your application targets Windows, you're probably better off trying to work within this restriction instead. There's only so much that libusb will try to abstract when the OS isn't exactly cooperative. Regards, /Pete ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
