Differences

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

--- aircraft:tmd:events [2019/07/20 15:52] – [Variables] jh
+++ aircraft:tmd:events [2019/07/20 15:58] – [event_timeout] jh
@@ Line 195: / Line 195: @@
   * Variable.Reset - The value is set to 0.0 (Value = 0.0)
-> Events are not limited to the variable class. Many, in fact almost all of the [[aircraf:tmd:input|TMD inputs]] can be manipulated in the same way as the variable. E.g. an ''input_binary'' can be Set, Reset or Toggled, an ''input_discrete'' can be Stepped, Toggled, Set or Reset as well.
+> Events are not limited to the variable class. Many, in fact almost all of the [[aircraft:tmd:inputs|TMD Inputs]] can be manipulated in the same way as the variable. E.g. an ''input_binary'' can be Set, Reset or Toggled, an ''input_discrete'' can be Stepped, Toggled, Set or Reset as well.
 <code>            <[variable][Variable][]
@@ Line 224: / Line 224: @@
 ==== event_timeout ====
+The timeout is an object like a countdown, several things can be fired here: .Trigger, .Set, .Reset, .Pause, .Unpause
+to start/stop/reset (like a chronometer), to start (let it run), reset (stop and reset) or pause and unpause the internal timer.
+''Duration'' is the count down time.
+When the timer has reached zero the list of ''Events'' are fired.
+> The event delay could theoretically restart itself causing a periodic check, but this should be avoided if possible as there are better ways to catch changes in a system state, e.g. the ''event_edge'' or to constantly monitor a value, e.g. logic_greater, logic_or, etc. (see [[aircraft:tmd:logic|TMD Logic]]).
 <code>            <[event_timeout][EventDelay][]
-                <[float64][Duration][1.0]>
+                <[float64][Duration][10.0]>
                 <[string8][Events][ DEV0.Trigger ]>
             >