override touch with next touch

[SolarB]

I'm having an issue where an aiming reticule is set to x and y of a touch (or xmouse, ymouse).

However when I begin a new touch while still holding the previous one the reticule refuses to move to the new touch. This is annoying since I want players to immediately be able to aim wherever the next touch occurs even if they still have their fingers/thumbs down.

I have tried 'repeat while left mouse' and 'touch 0 is active'.

What would be sensible here is an action on the multiple touch object to the effect of 'any touch is active' rather than having to specify a number in order to override the previous touch.

I'm scared that if I use 'touch 0 is active' OR 'touch 1 is active' I may get some glitches.

Is there any workaround?


I hope this is clear


Thanks!

[Simon]

I am not at my machine now so can't check, but doesn't the multitouch object have a expression which returns the last touch number? Using this you can set your reticule to the position of touch (last touched)

[Francois]

Yes, you should use this. Actually, I should have never put direct access to touch by number. I think I will remove that in a future version.

[SolarB]

Thanks Simon and Francois, what I have now is:

+Touch LastNewTouch(multitouch) is active
--> set x("reticule") to XTouch( "Multiple Touch", LastNewTouch( "Multiple Touch" ))
--> set y("reticule") to YTouch( "Multiple Touch", LastNewTouch( "Multiple Touch" ))

and it works.

What I just realised though is if the user still has the touch before pressed down having released the new touch it would be good to have the reticule go straight back to the previous touch. I've thought about workarounds but each one would require double coding all actions to do with aiming/shooting (setting values/flags per touch) etc.

This is why I think a condition 'Any touch is active' then set x and y to 'current touch' would be a good thing.

Perhaps I still don't understand the difference between LastNewTouch and LastTouch. Could the above be achieved using this?

Thanks again for the help.

[Diablohead]

Yes, you should use this. Actually, I should have never put direct access to touch by number. I think I will remove that in a future version.

If you remove the touch number access won't this mess up stuff already set in events for people using it?

[Francois]

I will remove it only from the menus : the conditions and expressions will still be in the object and older applications will work.