On 15 February, 2016 - Willem Ferguson wrote:
>
>
> On 14/02/2016 23:13, Anton Lundin wrote:
> >On 14 February, 2016 - Willem Ferguson wrote:
> >
> >>Is there a way in android to check for a PID? You can imagine that
> >>the initial step of devising communication will be immensely
> >>complex.
>
On 14/02/2016 23:13, Anton Lundin wrote:
On 14 February, 2016 - Willem Ferguson wrote:
Is there a way in android to check for a PID? You can imagine that
the initial step of devising communication will be immensely
complex.
A PID is useless without the corresponding VID. We already have code
On 14 February, 2016 - Willem Ferguson wrote:
> On 14/02/2016 22:27, Anton Lundin wrote:
> >On 14 February, 2016 - Willem Ferguson wrote:
> >
> >>On 14/02/2016 06:13, Dirk Hohndel wrote:
> >>>On Sat, Feb 13, 2016 at 08:55:27PM +0200, Willem Ferguson wrote:
> I need to filter the above dive c
On 14/02/2016 22:27, Anton Lundin wrote:
On 14 February, 2016 - Willem Ferguson wrote:
On 14/02/2016 06:13, Dirk Hohndel wrote:
On Sat, Feb 13, 2016 at 08:55:27PM +0200, Willem Ferguson wrote:
I need to filter the above dive computer names to those with FTDI
interfaces. In libdivecomputer t
On 14 February, 2016 - Willem Ferguson wrote:
> On 14/02/2016 06:13, Dirk Hohndel wrote:
> >On Sat, Feb 13, 2016 at 08:55:27PM +0200, Willem Ferguson wrote:
> >> I need to filter the above dive computer names to those with FTDI
> >>interfaces. In libdivecomputer the dc_descriptor_t contains a lot
On 14/02/2016 06:13, Dirk Hohndel wrote:
On Sat, Feb 13, 2016 at 08:55:27PM +0200, Willem Ferguson wrote:
I need to filter the above dive computer names to those with FTDI
interfaces. In libdivecomputer the dc_descriptor_t contains a lot of
information, for instance the transport definition. I
On Sat, Feb 13, 2016 at 08:55:27PM +0200, Willem Ferguson wrote:
> >>1) I have now gone beyond the last patch that I submitted (I think 3 days
> >>ago) doing some first groundwork by removing some code from the usual
> >>binaries and putting it the downwnloadmanager class. Looks like that patch
Thank you for the comment. I realise you were uber-occupied the last week.
On 13/02/2016 19:45, Dirk Hohndel wrote:
Let's keep the conversation on list, please.
I have two requests:
1) I have now gone beyond the last patch that I submitted (I think 3 days ago)
doing some first groundwork by
