Keyboard

Windows Key

This node makes it possible to interact with a Ventuz scene via keyboard. It provides information whether a specific key is pressed or not. Additionally, it triggers events when a key is pressed or released.

If AutoDeactivate is enabled, this node will be automatically deactivated if the parent Hierarchy Container is blocked. The property Active determines if this node is active and if it should react on the key hits. The property Key defines which key the node listens for. To specify the key, click on the triangle in the Key property argument field and then press the desired key. It is also possible to specify a key combination like CTRL + P.

If SendEventArg is enabled the key code is send as argument via the KeyDown and KeyUp event which occur if the correct key is pressed.

The Emit method simulates a key stroke and the node behaves as if the specific key on the keyboard has been hit. In this case the KeyUp occurs one frame after the KeyDown event. This Emit can be used to build a Ventuz scene which works identically with a real keyboard and a virtual keyboard on a touch display.

In addition to the events described above, this node provides information about the state (NotPressed, Pressed) of a specific key and its code (KeyCode).

DirectInput Key

This node provides nearly the same functionality as Windows Key. But there are two differences: this node notices every key stroke inside and outside the Renderer window and even outside the Ventuz application. It is not possible to send the key code as argument via the events and it is not provided as an output property.

Copyright 2011 Ventuz Technology Group