Update:
> On Dec 4, 2017, at 10:13 AM, Dirk Hohndel wrote:
>
> Linus just merged the latest functional changes in libdivecomputer (which
> once again took some commits from our branch and made random changes to them,
> making the merging increasingly harder), but of course
> On Dec 4, 2017, at 4:38 PM, Jan Mulder wrote:
>
> Dirk Hohndel schreef op 2017-12-04 19:13:
>
>> Linus just merged the latest functional changes in libdivecomputer
>> (which once again took some commits from our branch and made random
>> changes to them, making the
Dirk Hohndel schreef op 2017-12-04 19:13:
Linus just merged the latest functional changes in libdivecomputer
(which once again took some commits from our branch and made random
changes to them, making the merging increasingly harder), but of
course not the iostream code...
I know that Jan had
Hi there,
Here's my rough plan.
Linus just merged the latest functional changes in libdivecomputer (which once
again took some commits from our branch and made random changes to them, making
the merging increasingly harder), but of course not the iostream code...
I know that Jan had a
On 4 December 2017 at 15:47, Jef Driesen wrote:
>
> Davide's data is the exception to the rule. It's the only dataset with CCR
> dives present, and an ADC offset of -1. I'm not sure what's going on there.
> The -1 could be a valid value here, but it would be really
On 2017-12-02 22:39, Anton Lundin wrote:
On 02 December, 2017 - Anton Lundin wrote:
I saw something odd looking at that data. There's another calibration
value in the data, which we never figured out the meaning of.
In all other sample data its bin zero or low values like 2. In your
data
its
I am surprised by some of the visual issues we are seeing on iOS. The same code
runs on Android without these problems. I'm not sure what we can do here...
/D
On December 3, 2017 3:13:13 AM PST, John Smith wrote:
>
>
>On 2 Dec 2017, at 21:11, Scott Ireland