summaryrefslogtreecommitdiffstats
path: root/core/parse-xml.c
diff options
context:
space:
mode:
authorGravatar Robert C. Helling <helling@atdotde.de>2016-06-14 17:12:57 +0200
committerGravatar Dirk Hohndel <dirk@hohndel.org>2016-06-14 12:04:36 -0700
commitfc213066f8ee9e129bdace3c042322df6c5cc611 (patch)
tree9f858148cb1d013a6ca34a937d429ff1505ba2d4 /core/parse-xml.c
parent0d986b9cfd400d774a540b80255d9cd53235cb5e (diff)
downloadsubsurface-fc213066f8ee9e129bdace3c042322df6c5cc611.tar.gz
Only setpoint changes with non-zero SP indicate a CCR dive
There might be some spurious setpoint changes at t=0 without an actual value (I have no idea where those come from). In any case, those do not indicate that the dive is a CCR dive. Signed-off-by: Robert C. Helling <helling@atdotde.de> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'core/parse-xml.c')
-rw-r--r--core/parse-xml.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/core/parse-xml.c b/core/parse-xml.c
index c79d7a9fc..3b5a2d794 100644
--- a/core/parse-xml.c
+++ b/core/parse-xml.c
@@ -1663,7 +1663,7 @@ static void event_end(void)
* Older logs might mark the dive to be CCR by having an "SP change" event at time 0:00. Better
* to mark them being CCR on import so no need for special treatments elsewhere on the code.
*/
- if (ev && cur_event.time.seconds == 0 && cur_event.type == SAMPLE_EVENT_PO2 && dc->divemode==OC) {
+ if (ev && cur_event.time.seconds == 0 && cur_event.type == SAMPLE_EVENT_PO2 && cur_event.value && dc->divemode==OC) {
dc->divemode = CCR;
}