On Thu, Dec 11, 2008 at 11:32:57AM -0500, Thomas Jaeger wrote: > I'm currently in the process of updating my gesture-recognition > application easystroke to reflect the XInput changes in xserver-1.6 and > I have a couple of questions about the direction that we're headed. > > The first question is about the behavior under core pointer freezes > caused by passive grabs with GrabModeSync. Currently, xserver-1.6's > behavior differs from xserver-1.5 in the following ways: > (1) While the core pointer is frozen, XInput events report the logical > state of the pointer, i.e. the point where the mouse was pressed down > (2) After the client calls XAllowEvents(dpy, ReplayPointer), the > complete motion history is replayed, but the coordinates reported are > the same as in (1), which isn't very useful. > > (1) is not a big deal, since the information about the physical position > of the pointer is still available through valuators. (2) would be an > improvement over the behavior in 1.5 if actual physical coordinates were > replayed, which is presumably what was intended here.
If that's the problem I'm thinking of, unfortunately that's unfixable. The spec actually demands that {event,root}_[xy] in events track the core pointer, not the current device. Awesome, isn't it? Cheers, Daniel
signature.asc
Description: Digital signature
_______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg