Hello
Because I ran into some unclear situations with keyboard bindings in case I have multiple bindings defined (concurrently) for one and the same key I tried to figure out how FG handles this.
As of now my understanding is the following:
- each binding is active and stored
--> this I see from /input/keyboard property tree
- conditions are stored as well
- if multiple bindings are fulfilling their condition(s) all of them are fired if the key is pressed ?
--> not sure about this one ??!
My problems:
I have binding #1 coming from keyboard.xml, it calls a nasal script depending on two properties defined as xml-condition tags
I have binding #2 coming from keyboard.xml, it toggles a property by command property-toggle and the same condition as binding #1
I have binding #3 coming from aircraft specific *-set.xml keyboard settings, it calls a different nasal script without conditions
I thought firsthand that the aircraft specific binding wins, and it seems to do so in some cases (other bindings I defined)
In the problem case however the aircraft specific binding doesn't fire ?!
My suspicion now is, that I ran into a bug, because from what I see in /input/keyboard it seems the condition of binding #1+binding #2 was copied to binding #3 despite my intention that binding #3 should fire unconditionally.
What could be a possible workaround so that binding #3 doesn't get the wrong condition ?
Thanks for any insight on this
Mike-DE