Archived

This topic is now archived and is closed to further replies.

n4gix

@g macro list

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

There is no list of @g macros :-)@g is just one macro used to simplify the reference to GPS variables.So what you need to do is search for those variables in the SDK.Tom

Share this post


Link to post
Share on other sites

Thanks, Tom,I really don't know where @g: variable reference is in the SDK. The @c: GPS variables are listed, but I still wonder about variables such as@g:enteringInput or@g:listCurrent etc, etcOver 70 of these used in the FS9 gps_500 xml, but I haven't yet found a reference for their use.I'll keep digging and at a later time maybe I'll have an answer or a more specific question.Regards,Bob

Share this post


Link to post
Share on other sites

There is no list. They're macros defined inside the xml for the GPS gauge. Period.

Share this post


Link to post
Share on other sites

>Got it. Won't ask again.I'll attempt to make it clear for you... @g is simply a :C:fs9gpsMacro's are merely a simpler replacement for a longer string of text, so in this instance instead of having to continuously type:C:fs9gpsone would only have to type:@gNote that in the G500 example, ACES has two s that are identical:C:fs9gpsC:fs9gpsAt first glance it might seem a bit silly to have @c and @g represent the exact same thing, but......a close examination of the XML script will show that they are using @c for "requests for information" and @g for sending "commands to the gps.dll"... at least, most of the time... ;)For example:70 (>@g:menuBlinker)This is a that is used to send "70" as a value to which the internal gps.dll variable named "menuBlinker" is set.So, anytime you need to reset the "menuBlinker" you would need only type @InitBlinker rather than the entire script, which when expanded would be:70 (>C:fs9gps:menuBlinker)Unfortunately for us, ACES has never documented any of the internal variables that they used within the gps.dll module, so we are left with no choice but to figure them out ourselves from inference (aka: guessing!)...In the FSX SDX though they have finally provided us a list of "things we can ask for" and some "things we can tell" the gps.dll but still have left out a lot of information... :-roll

Share this post


Link to post
Share on other sites

>@g:enteringInput >or>@g:listCurrent >etc, etc>>Over 70 of these used in the FS9 gps_500 xml, but I haven't>yet found a reference for their use.Unfortunately for us, ACES has never documented any of the internal variables/tokens that they used within the gps.dll module, so we are left with no choice but to figure them out ourselves from inference (aka: guessing!)...

Share this post


Link to post
Share on other sites