Lines Matching refs:GPE

64473     screen offset in GPE.
64475     Without this offset and the flag, GPE would simply add the offset of the
75839     Warps the pointer to the new spot and calls GPE with the x/y mask bits set.
85026     GPE unconditionally dereferences pDev->valuator if a mask is present. This
85195     keyboard (without valuators) has no effect as GPE ignores the event.
92718     Don't require every caller to use GPE + mieqEnqueue, provide matching
102790     Fix GPE Y axis scaling
103893     dix: get rid of the now-superfluous valuator arrays in GPE and friends.
107006     dix: copy the valuators passed into GPE/GKVE/GProxE.
107008     GPE and friends modify the valuators array passed in. Which means any driver
113415     xkb: use GPE for XKB fake motion events.
113419     POINTER_ACCELERATE flag for GPE, it would cause double-acceleration.
113421     Potential regression - GPE expects the coordinates to be either relative or
113435     In theory, an event coming in during GPE could reset our lastSlave, leading
121142     dmx: core events are always in screen coordinates when passed to GPE.
121147     Also mark the spot where we pass in the button state as valuator to GPE
124792     again. Instead of generating the event directly, GPE generates the event and
124817     GPE and friends now use internal events so they may generate up to 3 events.
132199     GPE and GProxE use the same.
133064     GPE, GKVE, GProxE generate InternalEvents now.
135759        scale them to device coordinates in GPE before continuing. Note that this
136089     dix: don't accept Button 0 presses in GPE.
137619     was obviously broken but nobody noticed. GPE had the correct version, but that
146885     Xext: use GPE/GKE from XTestFakeInput #16145
146889     much easier to just pass the variables into GPE/GKE and let the DIX do the
147121     Axis clipping wouldn't be necessary here, it's already performed in GPE.
147228     In GPE, we don't care about the device mode. Let's put the absolute values
147236     Revert "dix: Correct values in the device axisVal are calculated in GPE"
147238     We can't rely on GPE to update device->valuators->axisVal. If a SIGIO occurs
147308     dix: Correct values in the device axisVal are calculated in GPE
147316     dix: fill valuators with the correct values depending on the device mode (GPE)
147344     Make all conversion handling in GPE.
162763     causes GPE to blow up spectacularly, trying to get (and set) co-ordinates from
172189     Move GKE and GPE to a separate file, to help stem the events.c explosion.
172190     Mark GKE/GKVE/GPE as _X_EXPORT.
173994     GPE: fix absolute button events / GKVE: (non-XKB) don't repeat lock keys
173995     Fix absolute button events in GPE, where we would previously send valuator
174173     GKVE/GPE: have DDX allocate events
174174     Don't allocate events on every GKE/GKVE/GPE call, just have the DDX manage
174347     GPE: use button map for DBP/DBR, not just BP/BR
174376     xfree86 ddx: always free GKE/GPE events
174377     free() events we get passed back from GKE and GPE so we don't just, er,
175156     Convert KDrive to GPE/GKE interface.