added Greg to the CC, as I don't think he is on the list and he will want to
know about this
Hi,
On 09/25/2012 01:41 AM, Pete Batard wrote:
OK, since I'd like to use the 1.1 version change as an opportunity to slide
in a couple more API changes (set transfer codes to negative, as well as
Hi,
On 09/25/2012 09:57 AM, Hans de Goede wrote:
And 2 minutes after pressing send I realize I missed one, I guess we better
put this list on the wiki somewhere or some such ...
So for the list of desired API changes, for 1.1 you've planned AFAIK:
1) The bMaxPower change
2) Make transfer
Note that I had to revert a commit in github, as the initial 1.0.14
release broke the Windows backend, that had been updated to bMaxPower.
If you have been unlucky to pull from git within the last couple of
hours, expect git to be unhappy.
Also, since now of usbutils patches proposals I saw
a.k.a. 1.0.13, we hardly knew ye.
* Reverts the previous API change with regards to bMaxPower.
* Note that LIBUSBX_API_VERSION is *decreased* to 0x01FF and the
previous guidelines with regards to concurrent use of
MaxPower/bMaxPower still apply.
Regards,
/Pete
On Wed, Sep 26, 2012 at 4:00 AM, Frank Hibbeln fhibb...@wencomine.com wrote:
Sorry - I cant seem to find a Reply link for a message ( 29869217 ) posted
by Chuck Cook 2012-09-22 to the list so I hope this will find its way.
The OS is Windows XP. The app is being built with VStudio 2010.
Did
Lionel Debroux wrote:
The maintainer of libusb has proved, for two years, to be a roadblock on
the path of advancing the state of libusb and on making life easier for
users.
I think it would be fair of you to look closely at the repository
history before we discuss if and how I advanced the
On Wed, Sep 26, 2012 at 10:17 AM, Peter Stuge pe...@stuge.se wrote:
Alas I had tunnel vision on the master branch, noone helped me out of
that, and 1.0.9 took too long.
Glad that you recognized that.
I think it turned out very good once
it was done, but anyway, everyone is busy working on
