touch.index has near 0 relevance to multi touch gaming. it's only possible use is when you specifically want to organize based on a touch system of reducing and eliminating touches on a 0 based.
I cannot imagine any game where touch.index will be of use that isn't related to music.
prior to touch.touchID and touch.XYForID it was impossible to do multi touch input. Ashley gave it a try when I pushed subject on the difficulty. Thus now we have touchId. Still appreciate it :)
and yes excal it is sorta in a situation where you need to just get it right. I spent a month prior to touch.touchid and ForId to get dual analog working. I ended up using drag and drop behaviours instead of touch.index(as that was only natural multitouch available). It worked but it had a funny bit where the DD objects could not be stored in a sub folder for sorting :(
It's sorted out now.You can have dual/quad/hex/oct analog based controls now :P
=Group whatever=
var static tid = -1
onTouch Hudleft sprite
tid = -1
-- tid = touch.touchid
isTouching hud leftsprite
tid => 0
-- do your analog stuff
-- use touch.AbsoluteXForID or touch.XForId(you need to use ForId)
endTouch
touch.touchid = tid
-- end touch stuff
-- tid = -1
maybe you can minimize your capx and share it. I can barely effectivly read the images