Apparently it does support multitouch, it just does not have the proper software to make use of it.
One Comment
txmcse
I hope the video is correct, but i’m not sure it exposes what he thinks it does. I’ve been pouring over the android source trying to figure out about the resistive screen controls. I can tell you why the screen reacts the way it does.
The system and thus applications poll the core.sys.io.user.scrTouch api over and over 60 times a second. any touches to the screen are reported as and array with two dimensions. The menu application he is working with polls for touches of scrTouch.location, and searches from the maxX and MaxY until isContact==true.
So what he’s proving here is that the phone see the lowest point on the screen where a touch has occured. but the app stops there. it doesn’t continue to poll the screen and see where the next lowest touch is.
in fact, i was looking at the api… to see if i could write a simple app that would print an X on the screen at every location that was being pressed. I don’t see a method of scrTouch that will allow me to do it. now honestly… just because i can’t do it…. doesn’t at all mean it can’t be done.
so to wrap this up… it’s a cool test, but because of the way this app was written it only proves that the screen can see the ‘lowest touch’. it still remains to be seen if you and use the API to read multi touch.
I hope the video is correct, but i’m not sure it exposes what he thinks it does. I’ve been pouring over the android source trying to figure out about the resistive screen controls. I can tell you why the screen reacts the way it does.
The system and thus applications poll the core.sys.io.user.scrTouch api over and over 60 times a second. any touches to the screen are reported as and array with two dimensions. The menu application he is working with polls for touches of scrTouch.location, and searches from the maxX and MaxY until isContact==true.
So what he’s proving here is that the phone see the lowest point on the screen where a touch has occured. but the app stops there. it doesn’t continue to poll the screen and see where the next lowest touch is.
in fact, i was looking at the api… to see if i could write a simple app that would print an X on the screen at every location that was being pressed. I don’t see a method of scrTouch that will allow me to do it. now honestly… just because i can’t do it…. doesn’t at all mean it can’t be done.
so to wrap this up… it’s a cool test, but because of the way this app was written it only proves that the screen can see the ‘lowest touch’. it still remains to be seen if you and use the API to read multi touch.