Re: [Libusbx-devel] Asynchronous transfers without C-callbacks

2012-12-05 Thread Wolfgang Pupp
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; >

Re: [Libusbx-devel] Asynchronous transfers without C-callbacks

2012-12-05 Thread Tim Roberts
Wolfgang Pupp wrote: > I've been working with libusbx for some time now --I'm primarily very > happy with it-- but one design trait gave me trouble: Being forced to > use C-callbacks for dealing with asynchronous transfers. > It would be *really* nice if there was a "push style" API one could > res

[Libusbx-devel] Asynchronous transfers without C-callbacks

2012-12-05 Thread Wolfgang Pupp
I've been working with libusbx for some time now --I'm primarily very happy with it-- but one design trait gave me trouble: Being forced to use C-callbacks for dealing with asynchronous transfers. It would be *really* nice if there was a "push style" API one could resort to, like this: /* insid