Tim Roberts wrote:
> It's interesting you would call this "push style";
You're right, my bad- that should read "pull style".
> I don't see the point of the added complexity of the event count, which
> would be outdated as soon as it was returned. Why not just:
> libusb_transfer * transfer;
> while( libusb_get_completed_transfer( ctx, timeout, &transfer) ==
> some success value )
> {
> // Do something with transfer
> }
>
> In both cases, you'd have to loop back around to check later anyway.
Good point...
> This would not be too hard to add, although I suspect you could do the
> same thing yourself with a small C module.
I'm trying to avoid that for two reasons:
- Even the basic decision between implementing this directly *or* on
top of the current API (by using C-callbacks inside additional C-code)
is something I feel thoroughly unqualified to make (after having
looked around the sources for a little bit).
- I don't want to rely on a custom libusbx build because I like the
ability to use other peoples binaries (especially nice/helpful for a
LuaJIT binding, where I would only have to distribute Lua-script code
and could just make people download readily available libusbx dlls).
--Wolfgang
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
