No idea what interpretation you are talking about. There is generally a hard line: the driver reports cooked touch events to the framework, taking care of filtering and whatever else is needed to make them nice. The framework takes care of deciding what the UI does as a result of the cooked events (though of course this decision gets distributed around -- the window manager determines the window, the window in the application dispatches down its hierarchy, the view that receives it decides what it means).
On Wed, Nov 25, 2009 at 1:37 PM, nhopman <[email protected]> wrote: > Is interpretation of the touch behavior tunable below the application > layer? > > Tx > > N > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- Dianne Hackborn Android framework engineer [email protected] 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: [email protected] website: http://groups.google.com/group/android-porting
