Hi,
It's the old xinput patch and I just fix it without any crash this
time, I think, just to see how things should work in first place (to
implement basic NSTabletPoint etc). Currently only pressure is
working. The code is still very experimental. It registers all
possible input sources for all wi
I just look at how MotionNotify is handled, it does compress xmotion
event near the comment "Compress motion events to avoid flooding.", I
thought this was fixed but apparently this was fixed only in my tree.
If an user want to discard motion events, they should do that or
consider doing that at ap
Am 18.01.2011 20:44, schrieb Banlu Kemiyatorn:
> I just look at how MotionNotify is handled, it does compress xmotion
> event near the comment "Compress motion events to avoid flooding.", I
> thought this was fixed but apparently this was fixed only in my tree.
> If an user want to discard motion e
- Original message -
> I would like to disagree here. Condensing mouse move events is the right
> thing to do in most cases. 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
- 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 yo
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.
* NS
Hi,
This is a patch to enable xinput2 support which is incomplete but it
turns on tilt and pressure. I am not going to finish it for a while
but still suggest to have it reviewed and maintained in trunk so
someone may have enough interest to fix and finish and improve it to
support other devices. I
Sleepiness!
On Mon, Jan 24, 2011 at 3:41 AM, Banlu Kemiyatorn wrote:
> Hi,
> This is a patch to enable xinput2 support which is incomplete but it
> turns on tilt and pressure. I am not going to finish it for a while
> but still suggest to have it reviewed and maintained in trunk so
> someone may
On Sat, Jan 22, 2011 at 1:58 AM, Banlu Kemiyatorn wrote:
> 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,
> f
updated!
2011/1/24 Banlu Kemiyatorn :
> Sleepiness!
>
> On Mon, Jan 24, 2011 at 3:41 AM, Banlu Kemiyatorn wrote:
>> Hi,
>> This is a patch to enable xinput2 support which is incomplete but it
>> turns on tilt and pressure. I am not going to finish it for a while
>> but still suggest to have it re
On Wed, Jan 19, 2011 at 02:44:07AM +0700, Banlu Kemiyatorn wrote:
> I just look at how MotionNotify is handled, it does compress xmotion
> event near the comment "Compress motion events to avoid flooding.", I
> thought this was fixed but apparently this was fixed only in my tree.
If you're willing
On Tue, Jan 25, 2011 at 3:39 AM, Derek Fawcus
wrote:
> If you're willing to play with the so called 'device dependent' bits
> of NSEvent, there is API support for compressing/coalescing of events.
>
> See the NX_NONCOALSESCEDMASK value. I also seem to recall reading something
> about it only be
12 matches
Mail list logo
