<=  Resuming a track  

  Colorful events  =>

Sailor Logbook App manual
Special situations

General

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


Local TOC

Tracking disallowed (top)

As described in the Subscribe subpage chapter, there are some restrictions for non-subscribers.

One of these is disallowing tracking when historic data are older than 360 days.

Imagine you are a non-subscriber and have done some tracking. After a long pause you want to continue with this, so you tap   New track   only to see this:

Tracking disallowed

Choosing the second option, some old tracks are deleted, and   New track   tapped again; now the picture is:

Tracking disallowed

Tap   Help   for:

Tracking disallowed

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 interruption

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 interruption

Interruption of Notes is handled slightly different (notes cannot be resumed):

Handling interruption of a note

Long pause (top)

If you don't move during an extended period of time - approximately 15 minutes - and the App isn't in the foreground, the App will end the track for you. Provided you allow sending of notifications, 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, unless the App is in the foreground.

Unfortunately, there is an issue with automatic ending of tracking when in the background. Before iOS 13, this worked very reliably. At the time of writing (May 2020, iOS 13.4) the source of the issue is assumed to be iOS.

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.

Convergence of pins on map (top)

On the map, pins are rooted in plot locations. Somtimes more pins may want to occupy the same plot. Since only one pin at a time can be shown at a given location, pins are prioritized by type:

Convergence of an Event pin and the MaxSpeed pin (top)

Imagine that an Event pin and The MaxSpeed pin relate to the same plot - and both types are to be shown. The situation is illlustrated below with a three-part image:

Convergence of an event and MaxSpeed

The upper part shows a normal non-convergence situation - the popup displays maximum speed with prefix Max:

The middle part shows an occational convergence situation - the popup now displays maximum speed with prefix !Max! (over the red arrow).

The lower part shows the event pin which was obscured - the Show Boat & MaxSpeed pin option has been set OFF. The popup now also has a disclosure button to the right.

Convergence of an Event pin and a Periodic pin (top)

Now an Event pin and one of the Periodic pins relate the to same plot - and both types are to be shown. The situation is illlustrated below with a three-part image:

Convergence of an event and a periodic pin

Again, the upper part shows a normal non-convergence situation - the periodic pin popup displays Each 5 min

And the middle part shows an occational convergence situation - another periodic pin popup displays !Each 5 min! (over the red arrow).

The lower part shows the event pin which was obscured - the Show periodic pins option has been set OFF. The popup now also has a disclosure button to the right.


Sailor Logbook App manual - © Copyright 2018 CoaSoft ApS Denmark

<=  Resuming a track  

  Colorful events  =>

Sailor Logbook App manual
Special situations