Ray-intersection is a performance intensive operation due to the scene flexibility of Ventuz. When a new touch is detected, Ventuz will cast a ray to estimate which geometry (or Volume) the user has hit when the touch began (the same is done for touches which are hovering). Just inserting the interaction node automatically associates it with all geometries underneath it. The sphere however is neither affected by this nor does it itself react to touch input.
Multitouch paint update#
In the example shown here, touching any of the three rectangles and moving the touch will cause the Touch Translation to update its internal axis and thus move all nodes in its subtree. A Touch Paint node works like an Overlay Rectangle and automatically displays the texture that is painted by the touch movement.
For example, a Touch Translation node contains an axis inside and automatically performs the appropriate motion for the touch movement. Those values are both provided as output properties as well as used by the nodes themselves. The interaction nodes perform some calculations to translate the 2D touch position to meaningful values like the angle of rotation that is implied by the users movement in case of a Touch Rotation node. When a new touch is registered, Ventuz figures out which geometry has been touched and relates that information to all interaction nodes that are associated with it - all interaction nodes that lie on the path from the geometry to the scene root. As a consequence, it is not possible to limit the input information from hardware devices to specific nodes. Mouse (which is translated into a virtual touch when the left mouse button is pressed)Īll these sources of input are internally combined to one virtual touch device and therefore are treated exactly the same.Ventuz supports four forms of touch interaction: Instead, ease of use was the primary concern. Although much of the complexity of implementing Multi Touch has successfully been hidden from the user, a deeper understanding of what really goes on can seriously improve the way a user designs a Multi Touch scene.ĭue to the complexity of implementing a proper Multi Touch handling, the usual Ventuz philosophy of providing raw input information (as for example in the form of the Mouse Node) and the means to process them to the user has not been followed by the Multi Touch implementation. It describes the technical aspects of what happens internally from a touch being registered to the Interaction node reacting on it. This document presents an overview of the Multi Touch input handling and gesture recognition inside Ventuz. Input Processing, Smoothing & Interpolation.
0 kommentar(er)
