Re: getting old xinput patch to work.

[Banlu Kemiyatorn]

What if we implement NSTrackingArea and allow a property in that? So a
view that prefer the full motion/dragging will receive all the events.
How about this list?
* Property in NSTrackingArea demanding either motion, full motion,
full dragging with less motion and full dragging with no motion.
* NSApp sendEvent filtering so we don't need to make all backends to
support the mechanism.
* Backend support compression at system event level and/or invisible
sub xwindow to define the tracking area to lessen events in X's queue.

On Wed, Jan 19, 2011 at 5:23 PM, Banlu Kemiyatorn <address@hidden> wrote:
> ----- Original message -----
>
> There may be a few applications that want to
>> get all the movement events, even when they aren't fast enough to handle
>> them. (Although I really don't see what they could be doing with them in
>> this case)
>
> For this point, the app will handle them eventually, like you dont keep
> stroking the device for several minutes non-stop. Dense events usually
> happen in less than a second.



-- 
    .----.     Banlu Kemiyatorn
  /.../\...\   漫画家
 |.../  \...|  http://qstx.blogspot.com (Free Software Advocacy & Development)
 |../    \..|  http://feedbat.blogspot.com (Studio Work For Hire)
  \/      \/   http://groundzerostudiocomplex.blogspot.com (Studio Research)