search

IEHG / Portrayal-Catalogue

0 stars 0 forks source link

Alarms and warnings LUA scripts #3

Open gert-MORLION opened 5 months ago

gert-MORLION commented 5 months ago

S-101 is using an Alarm Catalogue which is part of the Portrayal Catalogue. This catalogue is handling the portrayal of alarms and warnings. The IEHG decided not to use such an Alarm Catalogue (yet). But this means that all procedures which are dealing with the alarms/warnings in the LUA scripts should be deleted.

S-401 is using the S-101 scripts if possible. Is there any reason to keep the alarm procedures in the S-401 scripts?

Example: -- Beacon Lateral main entry point. function BeaconLateral(feature, featurePortrayal, contextParameters) local viewingGroup featurePortrayal:AddInstructions('AlertReference:NavHazard;Hover:true')

gert-MORLION commented 3 months ago

During the S-401WG meeting in March, the proposal was made to keep all references to the alert catalogue and (temporarly) block the procedures behind the reference.

Because the alert references define which alert message has to be displayed, this would mean that the LUA script that is handling the alert messages should be 'blocked'.

An example of an alert is: "featurePortrayal:AddInstructions('AlertReference:NavHazard;Hover:true')" where "NavHazard" is an element of the Alert Catalogue xml file describing what the content of the message must be.

What's the point of keeping the alert references in the individual S-401 scripts, if we do not use them?