Multi Touch In DAT
The Multi Touch In DAT is used for receiving messages and events from the Windows 7+ standard multi-touch API. It captures all the messages, where each new message changes the table it outputs. When a messages is added to the DAT, any script can be called pointing to the new message. The Multi Touch In DAT is most frequently sent to the Render Pick DAT.
It can output either of two table formats: (1) Raw Events as a FIFO (first in - first out) list, or (2) ID Table, which is the events processed into a more usable one-row-per-finger table.
The Raw Events format creates a FIFO-type DAT (see also FIFO DAT) which, for each multi-touch event, has a row added to the bottom of the table while at the same time a row at the top is deleted.
Note: To operate panel gadgets with multi-touch screens that send events through the Windows 7, 8 or 10 event stream, multi-touch works without requiring DATs. You need to use the DAT when using multiple fingers on one panel, like in a container displaying a 3D render whose objects you want to pick.
The ID table format includes the columns:
id- every finger press increases the id by 1
sn- an ongoing count of each finger press.
select- when 1, this row represents a finger is down.
downf- the absolute frame number when the finger press occurred.
upf- the absolute frame number that the finger press ended
y- the position, in pixels in the horizontal and vertical directions.
yvalues are expressed in screen pixels, not panel width/height pixels. For example, the top-right corner of a panel will be different if the panel is scaled within another panel, window or network viewer. It is better to use
v, and scale them by the panel Width and Height.
v- the position, 0 to 1 in the horizontal and vertical directions
downv- the position, 0 to 1 in the horizontal and vertical directions when the touch first occured (ie. initial touch down location).
contacty - the width of the contact area.
contactv - the height of the contact area.
monitor- monitor number, starting with 0
downf, in seconds
elapsedtime- the number of seconds that finger has been down.
changedtime- the time since the finger press that the most recent u or v value changed.
dclick- double-tap occurred
aux- user supplied data via the PanelCOMP_Class method
interactTouch(). When the event is triggered by the mouse via the Include Mouse option,
auxwill include the mouse buttons used (
4for right, can be tested bitwise).
You can use the attached callback DAT (named
mtouchin1_callbacks) to react to multi-touch events. This is suitable for 2D interfaces that do not require a Render Pick DAT.
See also the MultiTouch page.
Parameters - Multi Touch In Page
active - Registers event when Active is On.
outputtype - ⊞ - Sets how the output is displayed in the table.
- Raw Events
log- Events are added to the table in a first in - first out (FIFO) order.
- ID Table
changes- Events are processed using one-row-per-finger in the table.
panel - The Panel Component to capture the touch events from.
relativeid - Reorder the touch ids so only the ones within the specified panel are counted.
relativepos - Output position and normalized coordinates relative to lower left corner of the specified panel.
mouse - When on, the mouse add a touch event when clicked. This event always shares ID 1 with the first touch. Using mouse and multitouch at the same time may result in unexpected behaviours.
posthresh - A new message will not be added if a finger has moved less than this number of units. The units are determined by the input device, not necessarily the resolution of the screen that it is associated with.
contactthresh - Some touch devices have a width and height of a press, representing pressure of amount of finger contact. This is a minimum threshold below which no events are recognized.
Min Rows Displayed
minrows - The minimum number of rows always displayed in the table.
Double Click (secs)
doubleclickthresh - The maximum time allowed between clicks to be registered as a 'double-click'.
Parameters - Received Messages Page
executeloc - ⊞ - Determines the location the script is run from.
- Current Node
current- The script is executed from the current node location (for example, where 'cc' points to).
- Callbacks DAT
- Specified Operator
op- The script is executed from the component specified in the Component parameter below.
fromop - The path that the script will be executed from if the Execute From parameter is set to Specified Operator.
clamp - The DAT is limited to 100 messages by default but with Clamp Output, this can be set to anything including unlimited.
maxlines - Limits the number of messages, older messages are removed from the list first.
clear - Deletes all lines except the heading. To clear with a script command, here is an example:
opparm -c /serial1 clear
Parameters - Common Page
language - ⊞ - Select how the DAT decides which script language to operate on.
input- The DAT uses the inputs script language.
node- The DAT uses it's own script language.
extension - ⊞ - Select the file extension this DAT should expose to external editors.
dat- various common file extensions.
- From Language
language- pick extension from DATs script language.
- Custom Extension
custom- Specify a custom extension.
customext - Specifiy the custom extension.
wordwrap - ⊞ - Enable Word Wrap for Node Display.
input- The DAT uses the inputs setting.
on- Turn on Word Wrap.
off- Turn off Word Wrap.
|• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •|
A custom interactive control panel built within TouchDesigner. Panels are created using Panel Components whose look is created entirely with TOPs.
Any of the procedural data operators. OPs do all the work in TouchDesigner. They "cook" and output data to other OPs, which ultimately result in new images, data and audio being generated. See Node.