Timeline for returning correct multiTouch id
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2012 at 10:10 | comment | added | MrCranky | You're certainly right to point out the problem with the inconsistent usage of id / i, but this problem won't be solved until the purpose of the ID is clearly understood (see my answer below) | |
| Sep 21, 2012 at 18:03 | comment | added | House | Please update your code sample to reflect the current state of the code. | |
| Sep 21, 2012 at 17:45 | comment | added | Green_qaue |
this gives the same effect as before, the multi-touch works but the speed increased if I shoot while moving.. And if I just spam-press everywhere on the screen for 10-15 seconds it gives me pointerIndex out of range exception. I dont think you need to use a loop like I'm doing, I was hoping that someone had experience with this kind of steering. Cus I'm pretty damn lost. thanks for yout suggestions tho mate!
|
|
| Sep 21, 2012 at 13:05 | comment | added | Green_qaue | Will do as soon as I get back from school :) thanks for the suggestion! | |
| Sep 21, 2012 at 2:45 | comment | added | House |
If you check out this documentation, you can see the example code uses the pointer integer for the getX() method. So try changing to the code I suggest above and see how it goes.
|
|
| Sep 21, 2012 at 1:32 | comment | added | House |
From what I understand event is really a list of events. You access the different events by going through the list like you're doing. So to access the x position for the second event you use event.getX(1) (since we're starting at 0). There are multiple xs, you're using the parameter to tell it which on you want. You're looping through all the events with your for loop, so use that number as the current event you're interested in. See my code change suggestion.
|
|
| Sep 21, 2012 at 1:32 | history | edited | House | CC BY-SA 3.0 |
added 832 characters in body
|
| Sep 21, 2012 at 1:09 | comment | added | Green_qaue |
aah, took me a while to understand your answer. but how will this work? if I use the same variable (x=event.getX(i)), then x will have to store 2 values whenever pointerCount is more then 1, correct? And that dosnt feel right.
|
|
| Sep 21, 2012 at 0:53 | comment | added | House |
Can you update the code in your question to reflect that? I see you removed the setting of x and y, but you are still getting the position by id later.
|
|
| Sep 21, 2012 at 0:26 | comment | added | Green_qaue | Agreed, if you down-vote. Let him know why. You are right its from a former method. Ive tried about a million different things so I just forgot to remove it. | |
| Sep 21, 2012 at 0:04 | history | edited | House | CC BY-SA 3.0 |
deleted 51 characters in body
|
| Sep 21, 2012 at 0:01 | comment | added | House | Care to comment on why this isn't useful and worthy of a downvote? It's the polite thing to do. | |
| Sep 20, 2012 at 23:03 | history | answered | House | CC BY-SA 3.0 |