Re: [Bitpim-devel] libusb / Darwin

[Roger B. <ro...@ro...>]

>   At least this set of data was all entered on the phone. If you can
> deal with it both ways, I think it's best to make the software tolerate
> it.

Yup, that is why the raiseonunterminated flag exists.  However I prefer
being rigorous on expectations of data to and from the phone until
shown otherwise.  If you are too lax, it is easy for bugs to get through
and bugs could lead to data corruption.

>> I have no idea what that is about.  The gauge is in the status bar
>> at the bottom.
> 
>   Again, this only happened if I had the protocol log running.
> Strange... Maybe it's some internal timing issue or threading conflict.

It would probably be quite hard to make a simple test case out
of which makes bug reporting it quite hard.
 
> and I did have to resize the main window to draw them.

I need to figure that one out.  Some of the widgets are quite temperamental
but magically behave well when resized.

Did you try writing back?  I managed to fill my phone with 70
images.  At the moment it doesn't do anything to the camera stuff
when writing back.  I'll probably leave it that way, since people
are unlikely to want to upload camera stuff.  (The download works
fine),

> In fact, since you connect
> by specifying the vendor/product/interface information, 

Only the sample code at the bottom of usb.py does that.  BitPim
itself calls usbscan.py to get a list of all devices and interfaces.
They are all uniquely named.

If you typed in an explicit name of the port, then _openusb in commport.py
finds that name and opens the endpoint.

If you browse the ports, then usbscan and comscan have their output joined
and comdiagnose produces some html describing each field in each port.

If you select 'auto' as the port, then usbscan and comscan have their
output joined, and comdiagnose picks out and prioritises which are
likely to be the phone.

Roger