I have exactly the same problem as you. It happens in the emulator and on devices, from 1.6 to 2.2. I was searching the web for a solution, but found nothing so far. But it's nice to know that programmatically we can get an accurate effect. It will get ugly implementing this in the app, but thanks for your findings.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
