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.

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

Are you looking for the "Button -> On clicked" event? Or do you have a sprite? In that case you may be looking for the "Touch -> On touched object" event. On either, you simply play the audio for the sound related to that button.

I completely removed the <font face="Courier New, Courier, mono">SecondTouchArea</font> and the problem still occurs:

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

Edit: Note, this was after I followed the steps from the bug post.

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.

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.

I guess I'm going to give this one last bump before I write up a bug report. I'd really hate for this to be an obvious problem.

Thanks!

You can use Audio's "Is tag playing" event. As long as you gave a tag to the audio file when you started it, you'll be able to use that same tag to test if it is playing.

I tried to use the Touch.YAt( Touch.Index ) and Touch.YForID( Touch.ID ). A very similar problem occurs: the blue <font face="Courier New, Courier, mono">SliderMarker</font> toggles between the Y values of the two touches.

In the past, I've tried to capture the Touch.ID of the finger that first touches the <font face="Courier New, Courier, mono">Slider</font>. The logic would then only allow a touch with that same Touch.ID to manipulate the <font face="Courier New, Courier, mono">SliderMarker</font>. Unfortunately, this did not work either.

Are there any other ideas?

Hi again! I've simplified the problem and provided more direct observations of what I'm seeing.

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

File: TouchFail.capx

HTML5 Export: http://machinecodegames.com/showoff/touchfail2

Video: http://youtu.be/ExbvFMWZEro

Am I completely missing how the "Is touching" event is supposed to work? Is there a better way to accomplish what I want? I'd like to think this is a bug in Construct 2, but I'm still so new to this way of expressing my intentions that I'm worried that I've overlooked something simple.

Thanks!

I'm working on a project with three touch areas (TouchFail.capx or browse to the HTML5 export). I've stripped my example to two touch areas.

The player may adjust a parameter using the slider and get extra points by moving around in the second touch area. The <font face="Courier New, Courier, mono">SliderMarker</font> adjusts to where the finger current currently is located on the Slider.

+ Touch: Is touching <font face="Courier New, Courier, mono">Slider</font>? <font face="Courier New, Courier, mono">SliderMarker</font>, Set Y to Touch.Y

+ Touch: Is touching <font face="Courier New, Courier, mono">SecondTouchArea</font>?

During my testing, the <font face="Courier New, Courier, mono">SliderMarker</font> adjusts to where the finger is currently touching the <font face="Courier New, Courier, mono">Slider</font>. I can also touch the <font face="Courier New, Courier, mono">SecondTouchArea</font> without problems.

When I branch out to different devices and/or different browsers, I see a new problem. When I'm touching the <font face="Courier New, Courier, mono">SecondTouchArea</font>, it sometimes takes control of the <font face="Courier New, Courier, mono">SliderMarker</font>.

I can make a video if it'll be clearer, but here's the testing steps:

1) Touch the <font face="Courier New, Courier, mono">Slider</font> and move around. Watch the <font face="Courier New, Courier, mono">SliderMarker</font> move with the finger

2) Drag off the <font face="Courier New, Courier, mono">Slider</font> and watch the <font face="Courier New, Courier, mono">SliderMarker</font> stop.

3) Drag back onto the <font face="Courier New, Courier, mono">Slider</font> and watching the <font face="Courier New, Courier, mono">SliderMarker</font> move again.

4) Repeat steps (1) through (3), this time moving a second finger inside the <font face="Courier New, Courier, mono">SecondTouchArea</font>.

The bug occurs in step (4): the <font face="Courier New, Courier, mono">SliderMarker</font> moves up and down with the finger in the <font face="Courier New, Courier, mono">SecondTouchArea</font>, and stays that way until both fingers are removed from the screen. Often times, I cannot control the <font face="Courier New, Courier, mono">SliderMarker</font> any more and have to restart the application.

Am I using the Construct 2 language wrong and/or is there a better way to do this? Or is this an issue with, say, Chrome on Android?

I feel like I've got too much junk here... if anybody needs me to provide some more information, please let me know and I'll get it.