<=  Overview of editors  

  Track editor checks  =>

Sailor Logbook S App manual
Event editor checks

Local TOC

Text-note checks (toc)

Partly for technical reasons, partly to protect the Sailor Logbook Website against hacking, some rules apply for texts. If broken, they are considered insecure.

Insecure texts are not saved in the App until corrected. Likewise, if a text is changed so its content is no longer secure, the change will not be saved.

Check the general description of the Event editor before continuing with this chapter.

All illustrations in this chapter are made with Event editor type With pickerwheels. However, the With pickerscreens type might just as well have been used: same rules and same error messages apply.

Before an event is created or modified, these checks are done:

Length (toc)

Event editor checks

No room for: Sometimes a note is good for jogging your memory, but keep it short!

Insecure words (toc)

Event editor checks

In this example, the word change could be used instead.

Insecure characters (toc)

Event editor checks

In the Track editor free-text Comments field, these restrictions don't apply.

Emojis (toc)

Event editor checks

Use text based emojis (smileys) instead ;)

Connected set checks (toc)

The Event editors comprise up to five attribute sets, each comprising two attributes. The Wind direction and force and the Current direction and force sets are connected sets. For example: you must set a wind direction after setting a wind force - and vice versa.

In these two sets, the attribute values may not conflict:

Wind direction and force (toc)

Event editor checks

In other words, these rules apply:

- and opposite.

Current direction and force (toc)

Event editor checks

Here similar rules apply:

- and opposite.


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

<=  Overview of editors  

  Track editor checks  =>

Sailor Logbook S App manual
Event editor checks