The file I pointed to is the definition for the data -- the first number is the class of event (like key or abs), the second number is the code (like 'a' or key or x for abs), and the third is the value. You should be seeing this data fairly directly reflected in pointer location, except with the coordinates scaled to the window.
On Wed, Sep 30, 2009 at 9:09 AM, Jesper Nordenberg <megagu...@gmail.com>wrote: > > On Sep 29, 8:30 pm, Dianne Hackborn <hack...@android.com> wrote: > > That event stream doesn't look good (though it doesn't look like you > > included the whole thing so it is hard to tell). You can interpret it > with > > these constants for the first and second number: > > > > http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;... > > > > (The constants are actually more complete in the standard kernel header, > but > > I don't remember as well how to find it.) > > I've managed to build and run Pointer Location, but it doesn't seem to > respond when I press the touch screen. > > Got any additional pointers on how to interpret the output from > 'getevent'? > > /Jesper Nordenberg > > > -- 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, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
