aircraft:tmd:events
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
aircraft:tmd:events [2019/07/20 15:52] – [Variables] jh | aircraft:tmd:events [2022/07/19 21:07] (current) – [event_edge] jh | ||
---|---|---|---|
Line 38: | Line 38: | ||
< | < | ||
- | < | + | < |
< | < | ||
> | > | ||
< | < | ||
- | < | + | < |
< | < | ||
> | > | ||
< | < | ||
- | < | + | < |
< | < | ||
> | > | ||
< | < | ||
- | < | + | < |
< | < | ||
< | < | ||
Line 56: | Line 56: | ||
> | > | ||
< | < | ||
- | < | + | < |
< | < | ||
< | < | ||
Line 64: | Line 64: | ||
==== event_edge ==== | ==== event_edge ==== | ||
- | The event_edge | + | The event_edge, event_edge_rising and event_edge_falling objects |
- | * '' | + | * '' |
- | * '' | + | * '' |
+ | * '' | ||
Line 73: | Line 74: | ||
< | < | ||
< | < | ||
- | <[bool][Rising][true]> | + | <[float64][Value][0.0]> |
- | <[bool][Falling][true]> | + | <[float64][Threshold][0.5]> |
+ | > | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | > | ||
+ | < | ||
+ | < | ||
+ | < | ||
< | < | ||
< | < | ||
Line 195: | Line 206: | ||
* Variable.Reset - The value is set to 0.0 (Value = 0.0) | * 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 '' | + | > 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 '' |
< | < | ||
Line 224: | Line 235: | ||
==== event_timeout ==== | ==== event_timeout ==== | ||
+ | The timeout is an object like a countdown, several things can be fired here: '' | ||
+ | to start/ | ||
+ | |||
+ | '' | ||
+ | |||
+ | When the timer has reached zero the list of '' | ||
+ | |||
+ | > 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 '' | ||
+ | |||
< | < | ||
- | < | + | < |
< | < | ||
> | > | ||
Line 231: | Line 251: | ||
==== event_repeat ==== | ==== event_repeat ==== | ||
+ | |||
+ | Constantly fires an event as long as the input condition is non-zero. When the input is above zero the '' | ||
+ | |||
+ | '' | ||
+ | |||
+ | > It is not intended to trigger a long chain of events, just to fluidly move an input back and forth like the directional gyro adjustment for example. | ||
< | < | ||
Line 242: | Line 268: | ||
==== event_swap ==== | ==== event_swap ==== | ||
+ | |||
+ | This can swap two values within the tmd, e.g. two variables or a variable and an '' | ||
+ | |||
+ | > The '' | ||
< | < |
aircraft/tmd/events.txt · Last modified: 2022/07/19 21:07 by jh