20,741
edits
Bindings: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 4: | Line 4: | ||
* Clicks a [[menu]] item | * Clicks a [[menu]] item | ||
* Interacts with a dialog (clicking a button, selecting list entries etc) | * Interacts with a dialog (clicking a button, selecting list entries etc) | ||
In other words, '''bindings''' are simply the term for '''actions''' that are associated with certain '''events''' in FlightGear. | |||
There are different types of events supported by various subsystems, but the resulting action that can be triggered will typically involve either a hard-coded command (a so called fgcommand), or a block of scripted code (using [[Nasal]]). Bindings can be parameterized/customized using properties as arguments that are passed to each binding as a props.Node object. | |||
And Nasal code can also be registered to become available as a dedicated fgcommand. | |||
You can assign multiple bindings to one object, button or key. Bindings may contain [[conditions]] to make them conditionally executed. Each binding must specify a command node with its particular type, see below. | You can assign multiple bindings to one object, button or key. Bindings may contain [[conditions]] to make them conditionally executed. Each binding must specify a command node with its particular type, see below. | ||