View Single Post
Posts: 26 | Thanked: 0 times | Joined on Sep 2009 @ São Paulo (Brazil)
#43
Originally Posted by gerbick View Post
But how much? I mean, all it has to do is notice that it's being utilized by two inputs and not one.

For what it's worth, I'm going by my kiosk background and it's not that much of a difference if any at all if you detect one or two (or multiple) inputs. You just have to code for that.
What people are talking about is the power consumption of the capacitive touchscreen itself, and not the CPU time spent interpreting the positions.

Although I'm not familiar with the capacitive touchscreen power consumption, I'm pretty sure that the screen backlight must use much more than that.

Either way, resistive should be less taxing on the battery.

I've played around with the iPhone 3GS and although I don't like Apple (due to all the constraints they imply) I must admit their interface (software and hardware, including the capacitive touchscreen) works VERY well. No delay at all when scrolling webpages or menus.

But, I want a decent phone running an open OS, be it Android (preferably) or the Maemo (I didn't know Maemo until someone sent me and N900 link).

The N900 is (today) what comes closer to what I want. I'm just a bit reluctant about how is it in real life. Some videos show some stuttering when scrolling or playing games. Also not really sure how they implemented the "1GB application memory" as the hardware only has 256MB of RAM. If they are using flash memory for that it would be slow and would probably kill the Flash Memory due to multiple rewrites.

Multi-touch is not a required feature, but it's usability is great for zooming or rotating objects. I didn't like the gesture they are using on the N900 to zoom in or out on the browser. Also don't know how easy it would be for me (or other community developers) to implement a different gesture.

Hmm, I went off-topic here. sorry!