Got you. You might admit that out of the millions who use Android, your single use case is something significantly less than 1%, so I might be excused form asking what you could possibly want it for. However the answer is still no, because it would be too easy to use inappropriately.
- Brill Pappin On 2012-12-01, at 11:26 AM, Kent Nixon <[email protected]> wrote: > For the record, I want to record user interactions and touch locations on the > keyboard for research purposes (I work as a research assistant at the > University of Pittsburgh). Just because YOU can't think of a legitimate need > for the information, doesn't mean there isn't one. > > Thanks for the answer, though. Simplifies my searching a lot. > > On Thursday, February 3, 2011 9:00:39 PM UTC-5, Brill Pappin wrote: > No. > That would make it way to easy to capture a users data without them > knowning. > > What could you possibly want that for anyway except to write a > nefarious app? > Whats the difference between just watching the input that your app > owns and collecting touch events from the keyboard app itself?? > > - Brill Pappin > > On Feb 1, 11:02 am, ekowus <[email protected]> wrote: > > Is there a way to add an onTouchListener to the on screen keyboard? > > For example, I would like to monitor on onPress, onRelease, etc. type > > events from the actual keyboard not the editText region. > > > > Thanks, -- 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
