<Update> section limitations

[ilya1502]

Is it correct that I can only have one per gauge file?

 

[adino]

Yep, although I believe I read somewhere trough the forums that Bill got a way to hack the system again by having more updates hidden in <visibility> tags not sure though it was in 2D or 3D gauges...

 

[Heretic]

In FS9 syntax, yes.

 

[ilya1502]

Thank you, guys.

Still can't master that FSX syntax

 

[Heretic]

<Element>
<Select>
<Value>
[Your code here]
</Value>
</Select>
</Element>

This works as well as any update tag and you can use it as often as you like.

 

[ilya1502]

This works as well as any update tag and you can use it as often as you like.

That actually crossed my mind, but I was hesitating. Because why then have the <update> tag at all?

 

[adino]

I use <update> tag to place lines long of code that only calculate and control system logic within the gauge. I use the <Element> or <Visibility> tags mainly to control Bitmap logic.

 

[tgibson]

The only advantage I know about is that you can directly control the update rate of the Update section, which is not possible in an Element. You can use timing code to do the same thing, of course, but that is a clumsier approach. So if I would have things that need an update only once per second (for example), I would put those into the Update section and put the rest into Elements.

 

[ilya1502]

The only advantage I know about is that you can directly control the update rate of the Update section, which is not possible in an Element. You can use timing code to do the same thing, of course, but that is a clumsier approach. So if I would have things that need an update only once per second (for example), I would put those into the Update section and put the rest into Elements.

Tom, this is interesting. How do I specify the update interval?

 

[rcbarend]

Tom, this is interesting. How do I specify the update interval?

<Update Frequency="*"/>

Where '*' is:
1: 1* per sec.
2: 2* per sec.
3: 3* per sec.
4: 4.5* per sec.
5 and 6: 6* per sec.
7,8 and 9: 9* per sec.
0: 18* per sec. (default, and maximum schedule rate)

But now Tom's remark
"" So if I would have things that need an update only once per second (for example), I would put those into the Update section and put the rest into Elements "
makes me doubt .....
I allways understood that if you specify the Frequency in a Update section, this schedule rate applies to the whole gauge (so all other subsequent Element sections too).
I'll test this again ....LoL

Rob

 

[rcbarend]

I allways understood that if you specify the Frequency in a Update section, this schedule rate applies to the whole gauge (so all other subsequent Element sections too).

Just made a simple test gauge, which proves my point …

<Gauge Name="TEST" Version="1.0">

<Image Name="test.bmp"/>

<Update Frequency="1">
(G:Var1) ++ (>G:Var1)
</Update>

<Element><Select><Value>
(G:Var2) ++ (>G:Var2)
</Value></Select></Element>

<Element><Select><Value>
(G:Var3) ++ (>G:Var3)
</Value></Select></Element>

<Element>
<Position X="2" Y="0"/>
<Text X="48" Y="10" Length="10" Font="arial bold" FontSize="8" Color="#FFFFFF" Adjust="Left" VerticalAdjust="Center">
<String>Var1</String>
</Text>
</Element>
<Element>
<Position X="50" Y="0"/>
<Text X="38" Y="10" Length="10" Font="arial bold" FontSize="8" Color="#FFFFFF" Adjust="Right" VerticalAdjust="Center">
<String>%((G:Var1))%!d!</String>
</Text>
</Element>

<Element>
<Position X="2" Y="10"/>
<Text X="48" Y="10" Length="10" Font="arial bold" FontSize="8" Color="#FFFFFF" Adjust="Left" VerticalAdjust="Center">
<String>Var2</String>
</Text>
</Element>
<Element>
<Position X="50" Y="10"/>
<Text X="38" Y="10" Length="10" Font="arial bold" FontSize="8" Color="#FFFFFF" Adjust="Right" VerticalAdjust="Center">
<String>%((G:Var2))%!d!</String>
</Text>
</Element>

<Element>
<Position X="2" Y="20"/>
<Text X="48" Y="10" Length="10" Font="arial bold" FontSize="8" Color="#FFFFFF" Adjust="Left" VerticalAdjust="Center">
<String>Var3</String>
</Text>
</Element>
<Element>
<Position X="50" Y="20"/>
<Text X="38" Y="10" Length="10" Font="arial bold" FontSize="8" Color="#FFFFFF" Adjust="Right" VerticalAdjust="Center">
<String>%((G:Var3))%!d!</String>
</Text>
</Element>

</Gauge>

G:Var1, but also G:var2 and 3 are incremented once per sec.

As a sidenote:
This (still) makes me wonder what the advantage is of using an Update section (other then for specifying the schedule freq. for the whole XML gauge) over using (multiple) Element sections.
In fact, other then for specifying the schedule rate, I don't see any advantage in using an Update section at all; since I suspect (but now I am guessing ...LoL) the max. code size restriction within one Element section in a gauge, is the same as within the (only one possible) Update section in an FS9-syntax XML gauge.
Or am I missing something ???

By the way, this is in FSX-Accell, but I doubt it's any different in FS9 or any P3D version.

Cheers,
Rob

 

[ilya1502]

Thank you, Rob. This information is invaluable.

 

[edetroit]

Just made a simple test gauge, which proves my point …

By the way, this is in FSX-Accell, but I doubt it's any different in FS9 or any P3D version.

Cheers,
Rob

FWIW I have tested Rob's code in FS9 and he is absolutely correct.

 

[Heretic]

Here's code for a general timer:

(P:ABSOLUTE TIME, seconds) (L:START TIME, seconds) - 1 >
  if{ (P:ABSOLUTE TIME, seconds) (>L:START TIME, seconds)
[Your code here]
}

The "1" specifies the update interval in seconds.

 

[n4gix]

In fact, other then for specifying the schedule rate, I don't see any advantage in using an Update section at all; since I suspect (but now I am guessing ...LoL) the max. code size restriction within one Element section in a gauge, is the same as within the (only one possible) Update section in an FS9-syntax XML gauge.
Or am I missing something ???

To me, the major advantage is that most - if not all - of your 'logic' is neatly contained in a single "askit" instead of being scattered willy-nilly in multiple <Element> sections...

 

[rcbarend]

Hi Bill,

I understand your point.
So its for reason of structuring the code.

But since most of my gauges are mainly control "logic" , I structure a gauge in sequential functions , each in their own Element.
At least I understand now that there's no "functional" reason to use either Update or Element sections.
So I guess it's just a matter of preference, and the type of gauge.

Rob

 

[taguilo]

Using Element scripts has an important advantage over Update, in that each <Value> script is individually treated, where Update script is a single chunk of code, even in FSX's multiple <Update> schema.

Therefore, <Value> is the perfect place to use one of the most powerful operators : quit.

So for example, if you have a very long initialization code that is only executed once per flight, or any other condtional long code, using quit will prevent the unwanted portion from being parsed. Perhaps not a big saving, but counts in a whole.


Tom

 

[gpxe0]

Hello guys

Sorry to jump in your conversation, but I have a related question, which is not fully answered by your comments so far.

I run p3d v4.5.

- in an XML gauge, can I have more than one <Update> object ?
- is there a size limit for the <Update> object ? Is that limit applicable for each object considered separately or for all the <Update> objects together ?
- if there is no frequenncy defined for the Updae, what is the number of cycles per second by default ?

Many thanks

 

[Heretic]

See the other thread.