Touch IDs not being assigned

Link to .capx file (required!):

https://dl.dropboxusercontent.com/s/s1m4htcwkjszy0f/TouchIDNotBeingAssigned.capx?token_hash=AAEqkLBauOIqJYWPkKblUztyijUMkSs9y8m1U7ULgs1BfQ&dl=1

Steps to reproduce:

1. Click on left side of screen.

2. Click on right side of screen.

Observed result:

No Touch IDs are ever assigned.

Expected result:

Touch IDs should be assigned.

Browsers affected:

Chrome: yes

Firefox: yes

Internet Explorer: yes

Operating system & service pack:

Windows 7 SP1

Construct 2 version:

125 (latest)

Closing, this is by design. When you use mouse input, the touch ID is always 0. You only get real touch IDs when using actual touch input.

Should I export this to a live server and show the touch IDs not being assigned there?

TouchIDTest

Try this on a mobile device and let me know if you are getting any Touch IDs.

On Windows 7 64 touchscreen I'm getting 2 for each side.

Ipad 3 40691595XX going up 1 each touch sometimes adding 0.9999995 per touch.

So its doing something....

What exactly Im not sure.

Hi newt,

Can you do me a favor and let me know if you're getting TouchIDs here?

Icarus

Sorry, nope on both.

That and Im not really interested in having you use 50 megs of storage on the pad.

50MBs of storage? The game download is 25MB.

Plus it can be cleared by clearing the cache.

I just tried this on a friend's tablet.

If only one touch is active: both TouchIDs = 0.

If two touches are active (simultaneous touches): both TouchIDs = 1.

So there's a problem here. TouchID is not being assigned unless two simultaneous touches are happening, and when that happens, both TouchIDs are the same.

TouchIDTest

Try this on a mobile device and let me know if you are getting any Touch IDs.

Ashley or Tom, give this a try. You'll see what I mean: if two simultaneous touches occur, both get the same TouchID.

It works with unique IDs each time on iOS. On Chrome for Android, the touch ID is always 0 for the first touch, and appears to go up to 1 for the second touch. This is perfectly correct behavior; the spec for touch events only requires the identifier be unique to all other active touches (because touch IDs are only useful for distinguishing simultaneous touches), so re-using a touch ID of 0 is perfectly valid. Since your events aren't really aware of multi-touch, it's hard to see this happening when you touch both sides at once, but the ID does go to 1.

Ashley, what might cause two touches to both have the same ID?

I haven't seen anything that shows two simultaneous touches having the same ID.