Testing v392 with OSTC Sport

[Werner Macho]

Hi!

Tried it 2 times yesterday and it was reproducible.
Going to copy the log today evening as I think it will still be
reproducible ;) (unless there is a new version out there)

And there is already the list in subsurface where you can choose from.
That's how I choose OSTC Sport and nothing happened while "accidentally"
OSTC3 worked.

regards
Werner

On Thu, Jul 13, 2017 at 3:39 PM, Matthias Heinrichs <
matthias.heinrichs at heinrichsweikamp.com> wrote:

> Am 13.07.2017 um 15:03 schrieb Dirk Hohndel:
>
>> It tries to associate Bluetooth names (and the correspondong addresses)
>> with known patterns for dive computer names. I'm actually surprised that
>> this didn't end up with an error that it can't determine the address - but
>> maybe the slightly odd BT names of the OSTC devices worked out in our
>> favor here and it was misdetected?
>>
>
> I'd prefer a small pop-up with a list to choose from (Detected devices).
> Makes this all a bit more robust and future proof. In case /we/ choose the
> rename the newest model different /again/.
>
> Divemate had the same problems and they now keep a list of all possible BT
> names in their code. I still use one of the earliest OSTC3 BLE prototypes
> personally and it still has it's default name like "BlueMod+SR", for
> example.
>
> Regards,
>         Matthias
>
>
> --
> heinrichs weikamp gmbh * Adlerstr. 7 * 79098 Freiburg * Germany
>
> Amtsgericht Freiburg HRB 713558 * Gerichtsstand Freiburg im Breisgau
> Geschäftsführer: Matthias Heinrichs, Christian Weikamp
>
> _______________________________________________
> subsurface mailing list
> subsurface at subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20170713/7ebb4640/attachment.html>