Lines Matching full:extension
11 <title>X11 Input Extension Porting Document</title>
50 <title>X11 Input Extension Porting Document</title>
54 X11 Input Extension into an X server.
58 Most of the functionality provided by the input extension is
63 This extension includes functions to enable and disable input extension devices,
65 and button mappings, and others. The only input extension requirements
73 The process of initializing input extension devices is similar to that used
82 type of implementation is supported by the input extension.
86 Input extension events generated by the X server use the same 32-byte xEvent
88 sent for input extension devices, requiring that multiple xEvents be generated
89 each time data is received from an input extension device. These xEvents are
90 combined into a single client XEvent by the input extension library. A later
91 section of this document describes the format and generation of input extension
95 <title>Initializing Extension Devices</title>
98 Extension input devices are initialized in the same manner as the core
129 | - RegisterOtherDevice (extension device)
141 | - init extension device by calling some of:
167 If deviceProc returns | - core devices are now enabled, extension
169 move the device from | through the input extension protocol
200 If the device is to be used as an extension device, DDX should instead
266 InitKeyboardDeviceStruct. Since input extension devices may support various
371 input extension devices with an autoStart value equal to FALSE. If this is
372 done, EnableDevice will skip all input extension devices during server
375 when called for input extension devices. This will cause ProcXOpenInputDevice
429 corresponding routine for extension input devices, since they do not all
431 initialization of the input classes supported by extension devices.
440 should be called for extension devices that have keys. It is passed a pointer
459 core X keyboard. It must be called explicitly for extension devices
468 should be called for extension devices that have buttons. It is passed a
486 core X pointer. It must be called explicitly for extension devices that
495 should be called for extension devices that have valuators. It is passed the
516 core X pointer. It must be called explicitly for extension devices that
525 should be called for core and extension devices that have valuators.
550 core X pointer. It must be called explicitly for core and extension devices
559 should be called for extension devices that can be focused. It is passed a
571 core X keyboard. It must be called explicitly for extension devices
581 should be called for extension absolute pointing devices that report proximity.
601 may be called for extension devices that support some or all of the
614 core X keyboard. It must be called explicitly for extension devices
625 should be called for extension devices that allow the setting of acceleration
639 core X pointer. It must be called explicitly for extension devices
648 should be called for extension devices that have LEDs.
670 and should be called for extension devices that have a bell.
688 and should be called for extension devices that have a display upon which a
711 and should be called for extension devices that have a display upon which an
755 Since the atom was already made when the input extension was initialized, the
761 <title>Closing Extension Devices</title>
772 DisableDevice is not called by any input extension routines. It can be
776 using the extension device has terminated or called XCloseDevice.
783 Several input extension protocol requests have
796 implementations that do not open extension input devices until requested
830 If all input extension devices are initialized when the server
928 device (which is now accessible through the input extension), it should call
969 keyboard (which has now become available as an input extension device)
985 <title>Input Extension Events</title>
988 Events accessed through the input extension are analogous to the core input
994 defined by the input extension. Their actual values will depend on which
1002 input extension constants needed by DDX are defined in the file
1007 Some events defined by the input extension contain more information than can
1055 In order to pass this information to the input extension library, two 32-byte
1075 xev->type = DeviceKeyPress; /* defined by input extension */
1134 xev->type = DeviceMotionNotify; /* defined by input extension */