<=  Some iPad screenshots  

  Word list and topics  =>

Sailor Logbook S App manual
Special situations

General

Purpose of this chapter: to briefly describe some situations that are not mentioned elsewhere.


Local TOC

Interruption (top)

If the App was interrupted while tracking, you will hear an alarm when you return to or restart the App. Tracking will have stopped, and you will see a message:

Handling interrupt

The last plot will be assigned an event with the text Interrupt plot.

If interruption occurs before a minimum number (three) of locations has be plotted, the message is:

Handling interrupt

Long pause (top)

If you don't move during an extended period of time - approximately 15 minutes - tracking will stop to save battery, and the App will sound an alarm if it's in the foreground. A message notifies when it happened:

specSituations_longPause.png

This means that if you don't explicitly end a track when arriving to a harbor, the App will end it for you.

The last plot will be assigned an event with the text Pause plot.

If you allowed Notification authorization, a notification similar to the message above appears if the App is in the background or your device is turned off.

Duplicate key issues (top)

In the App, plots and attached events are assigned timestamps measured in seconds. Incidentally - though very seldom - two plots / events may get the same timestamp, e.g. a periodic and a manual event can occur in the same second. That's ok, since the App has no requirement that timestamps are unique.

At the Sailor Logbook Website plots and events are stored with timestamp values copied from the App. However, here uniqueness is required. Therefore, if the situation occurs that two plots / events have same timestamp, the second of these is skipped. The upload screen informs on this:

specSituations_duplicateKeys.png

Sailor Logbook S App manual - © Copyright 2018 CoaSoft ApS Denmark

<=  Some iPad screenshots  

  Word list and topics  =>

Sailor Logbook S App manual
Special situations