Hi guys,
In software "Target GUI", the key command release order don't match with pressed order.
when you press an key with modifier, the previous pressed keys should be released in the invert order.

For instance :

- Press Type : Pulse :
Key Press L_SHIFT (1)
Key Press L_CTL (2)
Key Press UARROW (3)
Key Release UARROW (3)
Key Release L_SHIFT (1)
Key Release L_CTL (2)


Order is : Press 1,2,3 - Release 3,1,2 (bad order)


- Press Type : Hold :
Key Press L_SHIFT (1)
Key Press L_CTL (2)
Key Press UARROW (3)
Key Release L_SHIFT (1)
Key Release L_CTL (2)
Key Release UARROW (3)

Order is : Press 1,2,3 - Release 1,2,3 (bad order)


- Press Type : Hold and Pulse : (Wanted solution)
Key Press L_SHIFT (1)
Key Press L_CTL (2)
Key Press UARROW (3)
Key Release UARROW (3)
Key Release L_CTL (2)
Key Release L_SHIFT (1)

order is : Press 1,2,3 - Release 3,2,1 (good order)

The problem is that in Falcon BMS, the Key command order is important. Otherwise in the simulator, the action key pressed are not released

How can i correct this ?
Thank you all for reading and helps.

If the key order is important, you need to create a chain, which will preserve the order.

This code simulates an UARROW pulse when you press S2.
If you are using GUI, you can also create a chain of 6 events which will generate the above MapKey (you can verify by using <ViewScript> button).

For HOLD, you will create 2 chains of 3 events each, one for press and one for release.

Yes you are right !
That was what i'm thinking about. But in this solution in Target GUI, you must create 6 évents. This one increase the risk to create parasitic effect !
Thank for your reply.

You can then use LOCK for ensure the complete chain is done first or maybe use UP/DOWN to coordinate the release order.