HP Workstation zx6000 HP Graphics Administration Guide for HP-UX 11.X (IPF ver - Page 21

InputDevice InputDevice, Identifier, Driver, ServerLayout

Page 21 highlights

configuring an X Server on HP-UX InputDevice section An InputDevice section is considered active if there is a reference to it in the active ServerLayout section. There may be multiple InputDevice sections. There are normally at least two: one for the core (primary) keyboard, and one for the core pointer. InputDevice sections have the following format: Section "InputDevice" Identifier Driver [Option ...] . . . EndSection "InputDeviceID" "DriverName" The Identifier entry specifies the unique name for this input device and must match an InputDeviceID in the active ServerLayout section in order to be active. The Driver entry specifies the name of the driver to use for this input device. InputDevice sections recognize some driver-independent Options, which are described here. See the individual input driver manual pages for a description of the device-specific options that can be entered here. Option Options for InputDevice Section Value Description CorePointer NA When this is set, the input device is installed as the core (primary) pointer device. There must be no more than one core pointer. If this option is not set here, or in the ServerLayout section, or from the -pointer command line option, then the first input device that is capable of being used as a core pointer is selected as the core pointer. Source: XF86Config manual page. CoreKeyboard NA When this is set, the input device is to be installed as the core (primary) keyboard device. There must be no more than one core keyboard. If this option is not set here, or in the ServerLayout section, then the first input device that is capable of being used as a core keyboard is selected as the core keyboard. Source: XF86Config manual page. AlwaysCoreSendCoreEvents boolean Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow additional pointer devices to generate core pointer events (such as moving the cursor, etc). Source: XF86Config manual page. HistorySize integer Sets the motion history size. Default: 0. Source: XF86Config manual page. Graphics Administration Guide 4-9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66

Graphics Administration Guide
4–9
configuring an X Server on HP-UX
InputDevice section
An
InputDevice
section is considered active if there is a reference to it in the active
ServerLayout section. There may be multiple InputDevice sections. There are normally at least
two: one for the core (primary) keyboard, and one for the core pointer. InputDevice
sections have
the following format:
Section “InputDevice”
Identifier
“InputDeviceID”
Driver
“DriverName”
[Option …]
. . .
EndSection
The
Identifier
entry specifies the unique name for this input device and must match an
InputDeviceID in the active ServerLayout section in order to be active.
The
Driver
entry specifies the name of the driver to use for this input device.
InputDevice
sections recognize some driver-independent Options, which are described here. See
the individual input driver manual pages for a description of the device-specific options that can
be entered here.
Options for InputDevice Section
Option
Value
Description
CorePointer
NA
When this is set, the input device is installed as the
core (primary) pointer device. There must be no more
than one core pointer. If this option is not set here, or
in the
ServerLayout
section, or from the -pointer
command line option, then the first input device that is
capable of being used as a core pointer is selected as
the core pointer. Source: XF86Config manual page.
CoreKeyboard
NA
When this is set, the input device is to be installed as
the core (primary) keyboard device. There must be no
more than one core keyboard. If this option is not set
here, or in the
ServerLayout
section, then the first
input device that is capable of being used as a core
keyboard is selected as the core keyboard. Source:
XF86Config manual page.
AlwaysCoreSendCoreEvents
boolean
Both of these options are equivalent, and when
enabled cause the input device to always report core
events. This can be used, for example, to allow
additional pointer devices to generate core pointer
events (such as moving the cursor, etc). Source:
XF86Config manual page.
HistorySize
integer
Sets the motion history size. Default: 0. Source:
XF86Config manual page.