I have integrated libxi2's capability to provide raw motion pointer values into
my application which was originally using (and still uses) xinput events. The
application currently registers for the old xinput events using XSelectInput.
XSelectInput(xs-dpy, xs-w, event_mask);
where
In trying to understand a heap corruption when I added XI2 RawMotion event
handling to our Xinput-based application, I came across the following routine
copyRawEvent() in libxi-1.3/src/XExtInt.c. My question is what is the purpose
of computing len if it is not used? Should it have been used
+roger.cruz=virtualcomputer@lists.freedesktop.org on
behalf of Roger Cruz
Sent: Mon 4/25/2011 3:35 PM
To: xorg@lists.freedesktop.org
Subject: XI2's copyRawEvent() question
In trying to understand a heap corruption when I added XI2 RawMotion event
handling to our Xinput-based application, I came
