04-05-2011 06:15 PM
The simulator allows for simulating single-touch capabilities. Two questions:
1. Is there a way to test multi-touch capabilities on the simulator?
2. Is there a way to turn off multi-touch capability in my app since I have not yet been able to test what happens if two or more simultaneous "touches" occur.
Thanks for anyone who has some ideas on these items.
Solved! Go to Solution.
04-05-2011 07:14 PM
Hope that clears a few things up. good luck!
04-05-2011 07:52 PM
In one of the webcasts there was talk about being able test multi-touch in the sim but RIM wasn't sure how to do it. With only 2 weeks before the latest launch date we probably won't be able test it like alot of other things. Maybe we can with a real playbook. Who knows.
04-05-2011 07:54 PM
04-05-2011 08:44 PM
04-05-2011 08:44 PM
04-05-2011 09:25 PM
Thank you for the response. A little more background to my second question regarding how my app might or might not work properly when on a real PlayBook:
- the app has a 'playlist' that allows items in the playlist to be (i) moved around (by touching and moving your finger around) on a particular item in the playlist, (ii) deleted (by touching an X box at the top right of each item in the playlist), and (iii) selected to be played by touching and lifting (ie "clicking"). My issue / question is that I am not quite sure what happens if one finger is being used to 'move' an item (ie touching an item, holding that finger on the item and moving it around), while another finger clicks on the delete X on another item in the playlist. I 'think' I know what will happen and that it will work, but I have not had a good way of testing it .. hence the question.
So in a sense, although my app is not specifically looking to respond to a multitouch gesture, it is possible that a user might try to do separate things at once that I hadn't anticipated and somehow the app won't work properly.
I guess I could turn off all other touching event listeners when a finger touch happens, and then turn them all back on again when the person lifts the finger off -- it's just not something you had to do when all a user could do was click in one spot at a time.
04-05-2011 10:50 PM
JRab and I actually discussed just this point, way back (Jan? Dec?). I could try to find the thread if it mattered much.
Our conclusion, as I recall was that there were two main options. Either the first touch point is treated as a mouse (MOUSE_DOWN, MOVE, etc), and any secondary or later (simultaneous) touch points would be ignored, or a secondary touch would effectively trigger the first to get fake MOUSE_UP and then the new touch would get a MOUSE_DOWN, becoming the new mouse position.
The latter possibility was rejected as basically insane, so we figured it's the first.
That would mean that once you touch, and keep your finger down, no other touches are recognized until you release the first finger.
It seems likely that this would be basically like a special case of what would happen with touch input, where only four touch points are supported and you try to touch a fifth point at the same time. It wouldn't make sense for the fifth point to be recognized... doing so would imply that even a mere stray "brush" of a finger would screw up recognition of the real touches.
We could have guessed totally wrong, however, and maybe there's a third or fourth possibility we hadn't considered.