20,741
edits
State machines: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
{{infobox subsystem | |||
|name =State machine support for the Autopilot system | |||
|started= 01/2013 | |||
|description = supporting state machines in autopilot XML config files | |||
|status = Under active development as of 01/2013 | |||
|developers = [[User:TheTom]] (since 01/2013), | |||
}} | |||
XML autopilot modules already support stateful components, especially JK and RS [[Autopilot_Configuration_Reference#Flip_Flop|flip-flops]]. The intention is to add explicit state-machine support, where a state machine component can be defined, with states and transitions between states. | XML autopilot modules already support stateful components, especially JK and RS [[Autopilot_Configuration_Reference#Flip_Flop|flip-flops]]. The intention is to add explicit state-machine support, where a state machine component can be defined, with states and transitions between states. | ||
| Line 28: | Line 37: | ||
* We already have good support for conditional expressions, bindings and computational expressions in SimGear. The intention would be to build upon these so the syntax and logic is familiar to people. | * We already have good support for conditional expressions, bindings and computational expressions in SimGear. The intention would be to build upon these so the syntax and logic is familiar to people. | ||
* Good inspector / debug support will help, as for the existing components. Especially, logging when state transitions occur, and when a transition becomes enabled or disabled. | * Good inspector / debug support will help, as for the existing components. Especially, logging when state transitions occur, and when a transition becomes enabled or disabled. | ||
[[Category:Developer Plans]] | |||