Is Key Pressed 2.0.5

[infuzion]

New: the IsKeyPressed has a new trigger input which you can use to poll whether the key has been pressed

So, does that mean if a Tick25 is not attached, you can not tell if the key has been pressed now in SM2.0.5?

[Tzarls]

As far as I remember, that´s the way it has always been. The only difference is that now you have a separate input for the trigger, while before the update, you had to connect the trigger to the "s" input.

[infuzion]

As far as I remember, that´s the way it has always been. The only difference is that now you have a separate input for the trigger, while before the update, you had to connect the trigger to the "s" input.

IIRC it was passive, & didn't need the trigger?

[trogluddite]

AFAIK, there's no change at all in its behaviour.. A trigger has always been required (possibly from the string changing) for a reliable poll of the keyboard - though maybe 'reverse' triggers from downstream components also used to work, can't quite remember.

Even the triggers at the string input are still passed through. That seems weird - now that there's a separate trigger input, it seems more sensible to me to not pass the string input triggers - would save having to remember to use a trigger blocker if you don't want a change of string to also poll the keyboard, and make the function of the primitive even more explicit.

[tester]

How to make this thing "is key pressed" to send only 1 trigger (not boolean value), and only when correct/defined key is pressed? It sends triggers in irrational way or I don't understand it?

[stw]

How to make this thing "is key pressed" to send only 1 trigger (not boolean value), and only when correct/defined key is pressed? It sends triggers in irrational way or I don't understand it?

Triggers should go out as they go in. You can use the "int changed" module to pass triggers only when the state changes.