Re: OSTCTools import support

2015-04-03 Thread Jef Driesen
On 2015-04-02 18:29, Dirk Hohndel wrote: On Sun, Mar 29, 2015 at 08:46:29PM +0200, Salvador Cuñat wrote: + +/* + * Parse data buffers instead of dc devices downloaded data. + * Intended to be used to parse profile data from binary files during import tasks. + * Actually included Uwatec

Re: OSTCTools import support

2015-04-03 Thread Salvador Cuñat
2015-04-03 9:13 GMT+02:00 Jef Driesen j...@libdivecomputer.org: The dc_parser_new() function requires a valid device handle. In this offline parsing scenario, you don't have that. That's a shortcoming which is already on my todo list: The dive callback of the dc_device_foreach() function

Re: OSTCTools import support

2015-04-03 Thread Salvador Cuñat
Good morning Dirk. 2015-04-02 18:18 GMT+02:00 Dirk Hohndel d...@hohndel.org: + dc_datetime_t datetime = { 0 }; so you renamed dt to datetime - nothing wrong with that, but it makes the patch more verbose and harder to see what's new, what's just renaming... - rc =

Re: OSTCTools import support

2015-04-03 Thread Salvador Cuñat
Good morning, again, ;-) 2015-04-02 18:29 GMT+02:00 Dirk Hohndel d...@hohndel.org: I think that we'll end up using something like this when doing the BT device communication in Subsurface. So this should be done in a generic way that allows us to take a buffer and hand it off to the correct

Re: OSTCTools import support

2015-04-03 Thread Anton Lundin
On 30 March, 2015 - Anton Lundin wrote: On 29 March, 2015 - Salvador Cuñat wrote: /snip All OSTCTools .dive files I could achieve are OSTC-2N/C series. It would be great to have some testing for logs from OSTC3, FROG or SPORT devices. Anton, Could you provide some .dive file from