Differences

This shows you the differences between two versions of the page.

--- gauges:spad.next_extensions [2016/01/29 11:45]
c0nnex [Extension to standard gauge tags]
+++ gauges:spad.next_extensions [2017/06/10 23:43] (current)
c0nnex
@@ Line 1: / Line 1: @@
 ====== SPAD.neXt Gauge Extensions ======
-===== Extensions for Expressions =====
+Gauges loaded into SPAD.neXt have to match this schema:{{:gauges:gauge.xsd|}}
-To access LVAR use the prefix **L:**
+SPAD.neXt is generally Saitek SaiSimFlightX compatible, but it has **NOT** implemented Saitek Bugs:
-Local Variables access
+Saitek gauges require a Non-Space-Character before a closing brace "}" e.g. in if{ statements:\\
+''if{ someexpression %} els{ someotherexpression %}''\\
+SPAD.neXt does not support this. You will need to alter the gauge accordingly and remove the **%**
+===== Extensions for Expressions =====
+To access [[:lvar_support|LVAR]] use the prefix **L:**\\
+<code>(L:AB_MCP_AP_ON, Number)</code>
+To access FSUIPC Offsets use the Prefix **F:**
+<code>(F:0000:0AB2, Number)</code>
+To access other simulation data use the prefix **T:SIMNAME:**\\
+<code>(T:PMDG737:1000:010E) or (T:PMDG737:Glareshield.Mode Control Panel.Altude)
+(T:SCS:scs/truck/fuel)
+(T:XPLANE:sim/cockpit2/annunciators/afterburner)</code>
+==== Local Variables access ====
 **X:**VARNAME = Local var , will not be saved, will always be initialized to 0´ when profile loaded\\
 **G:**VARNAME = Local var, Value will be saved to the //GAUGE//, loaded to that value again when the gauge is loaded\\
-**P:**VARNAME = Local var , Value will be saved to the //PROFILE// , and loaded to that value when the gauge is loaded
+**D:**VARNAME = Local var, Value will be saved to the //DEVICE//, loaded to that value again when the device is loaded\\
+**P:**VARNAME = Local var , Value will be saved to the //PROFILE// , and loaded to that value when the profile is loaded \\
+(Exception ''(P:SIMULATION RATE,Number)'' and ''(P:UNITS OF MEASURE,Number)'' still work as expected.
+==== Additional Time-Variables ====
+All time variables as shown [[https://msdn.microsoft.com/en-us/library/cc526981.aspx#EnvironmentData|here]] can be used with the "X:"-Prefix to retrieve the local computer time as UTC/Local.\\
+To get the local computer hour you would use
+<code>(X:LOCAL TIME,Hours)</code>
+==== Dynamic Images ====
-==== Image ====
 The Image-Tag supports the following extensions for dynamically changing images:\\
@@ Line 21: / Line 42: @@
 See: [[gauges:dynamic_images|Example for dynamic images]]
+==== Dynamic Labels ====
+In order to show numbers on the gauge, SPAD.neXt support an additional sub element:
+<Label>
+See: [[gauges:dynamic_labels|Dynamic Labels]]
+==== Extended Button Configuration ====
+To assign a function to a FIP button other than a SimConnect Control Event, you can deliver an extended button configuration together with your gauge.\\
+Just configure the button as desired within SPAD.neXt, and then export the button configuration (copy to clipboard and save to a file) to a file ''BUTTONNAME.bml'' in the gauge main directory.\\
+The following buttons are supported:\\
+''FIP_BUTTON_S1 - FIP_BUTTON_S6 , FIP_RIGHTDIAL, FIP_LEFTDIAL, FIP_BUTTON_PAGEUP, FIP_BUTTON_PAGEDOWN''
 ===== GaugeSettings =====

SPAD.neXt Wiki

User Tools

Site Tools

Differences

Page Tools