best touchscreen resolution (pixels/mm)

by Ken Schultz » Wed, 11 Feb 2009 20:34:31 GMT


Sponsored Links
 Does anyone know the best touchscreen resolution for Android?  Most
likely there would be a sweet spot for this.  The higher the
resolution the more data which could cause a bottleneck for data flow
and the low the resolution the worse the accuracy is.  I would imagine
this to be in the units pixels per millimeter.
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



best touchscreen resolution (pixels/mm)

by Dianne Hackborn » Wed, 11 Feb 2009 21:29:33 GMT


 Some that is at least the same resolution as the screen should be
sufficient.  Very few things -- certainly nothing that is part of the
standard platform -- is going to do much useful with sub-pixel touch data
(though we do report it in the APIs).






-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Other Threads

1. Android media player not reading ID3 tags

I wonder if anyone knows whether the built in media player uses some
kind of caching of mp3 files ID3 tag information, because after I
change the tag of a file it doesn't show the updated data. Only after
the phone restart, I guess after /sdcard remount, does it show correct
tag info.
Thanks

-- 

2. Mechanism for working with new hardware after docking

I'm wondering what the proper way is to dynamically load/integrate
device drivers for hardware that becomes available when a device is
docked.

For example, say a docking station has some new hardware on it that
our device could make use of (for the sake of illustration, let's say
it's some new Foobar IC chip). What is the 'proper' way for our device
to handle this scenario? Do we look for a docking event then attempt
to load this device driver? Do I need to create a new service to just
hang around looking for docking events and then attempt to access the
device (and any other devices that may be on the docking station)? Or
is there an existing mechanism (an existing service?) that I would
hook into that somehow enumerates new hardware (and drivers) that
becomes available? I'm thinking about this more at a system level (to
have the OS able to utilize the new devices) rather than at the
application layer.

Is there some sort of 'best practises' on how to have the system
support and begin using new hardware that becomes available
dynamically?

Any details, FAQs, or pointers to documentation related to this would
be very much appreciated.
Thanks!

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. sizing an activity window

4. Reporting bug in the Android Linux Kernel?

5. LG Ally from Verizon 2.1-update1 has broken apps

6. How to fix the Cursor Error (CursorWindow)

7. Android Porting Training in India