Haven’t done any multi-touch on Windows, but I imagine it works the same as mobile. Here’s a couple different ways of getting the inputs based on the touch index:
First method works well for individual events. Drag out the Finger Index output and type “switch” to get a nice little guy that redirects the exec based on which “finger” is touching the screen.
Second one works nicely for perpetual events, when you need to constantly create a vector based off of a swipe or finger:screen orientation or something like that. Doesn’t require an exec; just plug the outputs into whatever you need. Click the dropdown for your Finger Index options. These nodes will handle a single index, which is great for splitting up your perpetual/over-time actions into manageable chunks.