Refactored Digital Navigation Tool
Track symbol (example for simulation)
The following table describes the track label - type of sim - fields.
| Track Symbol Presentation | |
|---|---|
| Default label presentation without active input fields | |
 | |
| Id | Description |
| 1 | Alert text: UI.UpdateTRACK({..., alert: [0,1,2,3,4,5,6,7]}) |
| 2 | Attitude indicator: UI.UpdateTRACK({..., attitude: [-1,0,1]}) |
| 3 | Callsign: UI.UpdateTRACK({..., callsign: "new callsign"}) |
| 4 | Entry level: UI.UpdateTRACK({..., efl: [0..660]}) |
| 5 | Actual level: UI.UpdateTRACK({..., cfl: [0..660]})* |
| 6 | Exit level: UI.UpdateTRACK({..., xfl: [0..660]}) |
| 7 | COPN: UI.UpdateTRACK({..., copn: "copn"}) |
| 8 | COPX: UI.UpdateTRACK({..., copx: "copx"})** |
| ** Clicking on the COPX field, the heading selector window pops up. See below the sample. | |
|
|
| 9 | Track position indicator |
| 10 | Track heading indicator - if available |
| 11 | Label stick |
| * Default label presentation with active input fields - CFL input | |
|
|
| 12 | Label CFL input list |
Known statuses and alerts
The track statuses and alerts can be modified independently or in batch operation with other track parameter modifications.
| Track Status | ||
|---|---|---|
| Code | Description | Label presentation on UI |
| 0 | Hidden | Not visible on UI |
| 1 | Unconcerned |  |
| 2 | Preactivated |  |
| 3 | Active |  |
| The alerts - if set - appears on the top of the label. The alert text color applied on each alert status. Now I demonstrate alert on a sample active label. |
||
| 0 | No alert |  |
| 1 | RAM warning |  |
| 2 | CLAM warning |  |
| 3 | STCW warning |  |
| 4 | DAIW alert |  |
| 5 | STCA alert |  |
| 6 | CRASH alert |  |
| 7 | Out of Sector alert |  |
Characteristic point selector example
If user activates the heading selector window's input field, the field will contain the actual magnetic heading when the container window appears on the screen. If the virtual pilot wants to change the flight direction - using this mode, there are two options avaialble to achieve this.
a. Track heading modification: entering numeric value between range 0 - 359
degrees. After ENTER key pressed, the track will begin the turn - to
the *_shortest_* angle toward the desired track angle.
b. Type the name of the characteristic point - as the desired point name
forms in the input field, the list of the partially matched entries
from the characteristic points database will appear in a selection
window list. Clicking on the desired point, the track will find the
*_shortest_* angle to turn as above.
Please note: if input field background is not green, that means the point name could not be validated by pressing the ENTER key. Otherwise the app will look for the entered name in the database.
However it is still allowed to quick-select a point from the list by left clicking on the element in the list with mouse pointer.
In the latter case when virtual pilot starts to type the name of the characteristic point, its firs letter - and the redish background - indicates that the point is not defined (at least two characters must be given in the input to be able to validate the point name) The following image will present this phase of heading change using characteristic point.
| Heading selection with characteristic point name: one letter is in the input |
|---|
|
| Heading selection with characteristic point name: two letters are in the input |
|
| Heading selection with characteristic point name: two letters are in the input and the point selected |
|
Please NOTE that, the rolldown selection windows as well as the heading selector window itself would position themshelves out of the viewport if the target label is close enough to the border of the viewport.
Therefore is adviced to pan the viewport according to the position of the track label the user wants to work with.
-zg-