Algodoo

I had no idea what post step was for but I see now, thanks.

s_noonan,
Please explain how this is any better (it certainly is more complex) than just using keysIsDown() by itself in each of the three control boxes? I don't get it.

I'd rather you use onKey event for that. Much simpler handling.

Xray,

Q: Please explain how this is any better (it certainly is more complex) than just using keysIsDown() by itself in each of the three control boxes?
A: Benefits:

1. It can display the name of the function of the switch (for example, like "roar" in wild bill's raptor scene).
2. It displays the key that is used to do the function.
3. It displays the state of the switch.
4. It separates the states from the control logic. You can put code in the states without regard or caring about the logic.
5. It initiates state1 once, preventing multiple restarts of state1 even though the key is held down.
6. It sets the state to zero in a short time window after release of the key. This prevents constant resetting of the zero state and allows the state of the item being controlled to be set by the last key pressed.

If your point is that everything can be put into the keysIsDown() structure, then I agree with you. If you think that the logic structure can be simplified, then please show me how.

Kilinich,

The problem I have with

onKey := (e)=>{
keys.isDown(_key) ? {
_state1()
} : {
_state0()
}
};

is that _state1() will happen when the specific _key is pressed, but _state0() will happen when any keyboard key is released. This means that all the _state0()s will fire within the time of 1/sim.frequency in whatever order Algodoo decides. Please correct me if I am wrong.

And another thing, if you use the onKey event, and you are not in Algodoo play-mode, and you press a key that is also a short cut key, then the onKey event doesn't see the first press of your key. This doesn't happen when you put the code in the postStep event.

Is there a way how to lock shortcut key? so it will work always like in play-mode

Q: Is there a way how to lock shortcut key? so it will work always like in play-mode.
A: Yes, put key control code in the update event.

s_noonan,
I think JakubKubo was asking how to lock out the shortcut keys in order to prevent them from being active. And of course the answer to that would be, by placing: app.gui.playMode = sim.running in any update event.

Xray,
I agree. Thanks for clarifying that.