I am only throwing the permissions thing out there as it was the easiest to illustrate my point. I fully understand the implications of an app having the ability to take a screenshot. However, sometime this is a reasonable need by a user. What I was trying to say is that there must be a better way than to just say: It's a security risk therefore it is not feasible.
And you address that here: If/when we do have an API for an application to take a screenshot, this will probably be something along the lines of making a request for the screenshot, resulting in the system taking the screenshot and showing it to the user for them to confirm they want it given to the app before it is actually returned. That, to me, would be a perfectly acceptable solution where you would make it so there is no other option but to show what image the app just grabbed and it would be managed by the system. As far as permissions go and their vagueness making them useless... well that is a whole other debate. -- 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
