Searched refs:POINTER_SCREEN (Results 1 – 7 of 7) sorted by relevance
348 POINTER_ABSOLUTE | POINTER_SCREEN, &mask); in winEnqueueMotion()
189 POINTER_ABSOLUTE | POINTER_SCREEN, &mask); in enqueueMotion()733 POINTER_ABSOLUTE | POINTER_SCREEN, &mask); in dmxEnqueue()
852 if (flags & POINTER_SCREEN) in scale_from_screen()861 if (flags & POINTER_SCREEN) in scale_from_screen()1397 … if (flags & (POINTER_SCREEN | POINTER_DESKTOP)) { /* valuators are in screen/desktop coords */ in fill_pointer_events()1428 if (flags & POINTER_SCREEN) { in fill_pointer_events()
71 #define POINTER_SCREEN (1 << 4) /* Data in screen coordinates */ macro
745 POINTER_SCREEN | POINTER_ABSOLUTE | in miPointerMove()
512 POINTER_ABSOLUTE | POINTER_SCREEN, &mask); in dispatch_pointer_motion_event()
58181 Setting POINTER_SCREEN with a unset valuator mask causes a jump to 0/0. Set64476 current screen if POINTER_SCREEN is set.67435 POINTER_SCREEN coordinates are screen-relative. For a Zaphod setup, the69223 input coordinates for the POINTER_SCREEN case.119127 Xming: Add mouse motion events with flag POINTER_SCREEN in winEnqueueMotion()119129 Add mouse motion events with flag POINTER_SCREEN in winEnqueueMotion(), as126686 dix: deal with first_valuator > 0 correctly if POINTER_SCREEN is set131506 Xext: set POINTER_SCREEN flag in XTestFakeInput if necessary. (RH #490984)131508 The POINTER_SCREEN flag must be set explicitly for XTest core events to avoid