I am working on a touch-triggered visual installation that leverages Multi Touch In DAT. I am able to read the finger data through Multi Touch In DAT, however, unable to convert or reference the data to trigger the visual effect. Right now it only reads one finger that replaces the mouse U and V data.
Have a look in the palette at multiTouch. In the demo with the disks, look at the callbacks DAT
/project1/multiTouch/multiTouch/renderpick2_callbacks.
The example may be not quite what you need, but the important thing is that the onEvents() callback deals with all the events that came in the same frame, for all fingers and for all down presses, drags and releases.
So triggering the visual effect should happen from the onEvents() callback in the Render Pick DAT. For example you would trigger a Speed CHOP, Timer CHOP, Event CHOP, Trigger CHOP or Audio Play CHOP using a op(‘mychop’).par.somepulseparameter.pulse() function.
(I advise against simply grabbing from rows of the table, you will miss events.)
And the data that is available for each event is rich:
# u - The selection u coordinate. (float)
# v - The selection v coordinate. (float)
# select - True when a selection is ongoing. (bool)
# selectStart - True at the start of a selection. (bool)
# selectEnd - True at the end of a selection. (bool)
# selectedOp - First picked operator. (OP)
# selectedTexture - Texture coordinate of selectedOp. (Position)
# pickOp - Currently picked operator. (OP)
# pos - 3D position of picked point. (Position)
# texture - Texture coordinate of picked point. (Position)
# color - Color of picked point. (4-tuple)
# normal - Geometry normal of picked point. (Vector)
# depth - Post projection space depth. (float)
# instanceId - Instance ID of the object. (int)
# row - The row associated with this event (float)
# inValues - Dictionary of input DAT strings for the given row, where keys are column headers. (dict)
# custom - Dictionary of selected custom attributes