"Is touching" event broken?

Link to .capx file:

TouchFail.r126.capx or TouchFail.r127.capx

GUI snapshop:

<img src="http://machinecodegames.com/showoff/touchfail4/GUICapture.jpg" border="0">

Code snapshot:

<img src="http://machinecodegames.com/showoff/touchfail2/Construct2TouchProblem.jpg" border="0">

Steps to reproduce:

1. Touch the orange bar and slide around to move the blue bar.
2. While still touching the orange bar, touch elsewhere on the green.
3. Remove your finger from the orange bar and slide the other finger (the one touching elsewhere) around.

Observed result:

The blue bar moves whether or not the orange bar is being touched.

[TUBE]http://youtu.be/ExbvFMWZEro[/TUBE]

Expected result:

I expect the blue bar to move only when there is a touch on the orange bar and to only be affected by that touch.

I have tried storing off indexes, IDs, and positions of touches. You can look at other tries I've made at making this work on the "How do I..." forums (http://www.scirra.com/FORUM/topic66935.html)

Browsers affected:

Chrome: yes

Android 4.1.1 default browser: yes

PhoneGap Android: yes

Operating system & service pack:

Windows 8

Construct 2 version:

Both r126 and r127.

Edit: Other systems affected added.

We also have similar touching event problem too. Did you try previous release of r126?

I originally saw the problem under r126 and then made sure that it was still happening in r127. When testing under r127, I saw some different behavior, but the main problem was still there.

What kinds of problems are you seeing? Maybe if we could see this from different angles, the underlying problem will become more obvious.

Edit: I saw your issue here in this bug post. It does seem very similar to my issue. I've grown concerned that this isn't a bug, but just a misunderstanding in how to use Construct 2's language. In the documentation, they mention that the way that we are using "Is touching" should work for most cases, but imply that there are cases where you'll need to write a bit more code.

You can read http://www.scirra.com/FORUM/topic67148.html about our problem.

If this is a 'C2' bug it must be solved soon if we want to involve touch screen envoirement.

This is not a bug, your events are not multitouch aware. If there are two touches, Touch.Y or Touch.ID could return for either of them, which is not what you want but what your events say.

Here's a fixed version which is multi-touch aware: https://dl.dropboxusercontent.com/u/15217362/fixedtouchslider.capx

Closing as not a bug.

There is still a bug, even with your version.

First, for some reason, the version you uploaded doesn't work in Android Chrome at all (just a black screen).

When I put it into the default Android 4.1.1 browser, the blue bar jumps all over the place if a second finger is touching anywhere else on the screen.

Feel free to use my latest uploaded version: http://machinecodegames.com/showoff/touchfail7

Could I get confirmation that this post isn't being ignored?

Just for clarification, my code does a lot of things to keep the touches in check (including bounds checking, storing off touch IDs, etc.) But there is an underlying problem that hasn't been fixed.

I will upload a video to this post of the problem if I know this is being watched. But if this isn't being watched, I will open a new bug report.