High time-resolution for MultiTouch input


When parsing the data from the “Touch (Devices Window)” node in Enqueue mode, I noticed that the output is a queue where only one item gets popped off the stack per frame. The result is delayed data where the exact timestamp per touch event is lost.

The TOUCHINPUT C struct does define a timestamp (dwTime), but when looking at the implementation of the node, I see that this field is ignored and not sent to an output pin. If I want access to this I suppose I could write my own plugin, but I was just wondering if there is something I am overlooking. Is there any reason for this omission? Is the timestamp unreliable?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.