gaschange event at begin of dive?

[Jef Driesen]

On 2013-02-03 12:58, Jan Schubert wrote:
> On 02/03/13 02:17, Dirk Hohndel wrote:
>> Jan Schubert <Jan.Schubert at GMX.li> writes:
>>
>> > On 02/03/13 01:05, Jan Schubert wrote:
>> >> While testing around with the import from OSTC I just recognized 
>> that I
>> >> now get a gaschange event displayed at the very beginning of a 
>> dive. I'm
>> >> not absolutely but pretty sure this is new behaviour and has not 
>> been
>> >> there before. Checking older logs/xmls it is not there and in the
>> >> planner we suppress such events by purpose. Has there anything 
>> changed
>> >> or is this an unwanted feature introduced with the last patches?
>> >
>> > This "feature" is not there while downloading from Predator but 
>> only OSTC!?
>>
>> This should only happen if you "First Gas" is not Gas 0. Could that 
>> be
>> the case?
>
> Aehm, actually no, it is the 1st gas.

The initial gas change event from libdivecomputer is intentional. 
Because the current api reports gas changes, and not the active gas, how 
else would you figure out the initial gas? There is no reason why the 
initial gas has to be the first gas! There may be devices where that's 
indeed the case, but that doesn't have to be true.

With this in mind, the ostc behavior is actually the correct one, and 
all other backends have a bug here :-)

> But - again - I've to admit I
> did a OSTC firmware update to 2.60 which remembers me a discussion
> with Jef requesting a dump with dives using firmware >= 2.58.

That was for another purpose: to test the new gas mix active bits, and 
the merge of the OC and CC lists. I'm still interested in this data.

Jef