Gases in divelist

[Dirk Hohndel]

Miika Turkia <miika.turkia at gmail.com> writes:
>>> It is actually quite clear in the DB. If there is a heading value, it
>>> is always the heading. Otherwise this field is empty.
>>> sqlite> select * from Mark where DiveId = 305;
>>> DiveId|MarkTime|Type|Heading
>>> 305|2076|258|130
>>> 305|3341|19|
>>
>> So type 258 is a heading and type 19 is a bookmark? Or am I misreading this?
>
> Sorry for not explaining. The 258 is bookmark with heading of 130
> degrees. The 19 is surface. Most of the bookmarks I have seen do not
> have the heading at all, but some do (I suppose there is some logic so
> the heading is recorded only when relatively sure that we are heading
> that way).

Wow. Crazy.

>>>> Not sure what to do here. My gut feeling would be to say "whatever" and
>>>> just drop the value for bookmarks. What do people think?
>>>
>>> I can change the DM4 import to generate a heading event if that is
>>> preferred. Then we would have both bookmark and heading at same time.
>>
>> Well, only if there are two events, right?
>> I there is only a heading event in the database (as it appears to be at
>> time 2876 in the example above), why would you create a bookmark event
>> as well?
>
> I wonder if it is clear to the users that when there is heading event,
> that is actually the bookmark they stored. (Heading is recorded only
> when one stores a bookmark, otherwise there are no headings recorded
> at all.) Other than that I don't see any reason to store the bookmark
> event in this case.

Give that this is simply shown in the tooltip I think having the heading
event shown there will be clear enough.

/D