If you load the keymouselistener and dwellmouselistener GtkModules in the GDM configuration file, you can assign user actions to launch specific assistive technologies. These user actions are called gestures. The gesture associations are contained in the following GDM configuration files:
/etc/X11/gdm/modules/AccessKeyMouseEvents
/etc/X11/gdm/modules/AccessDwellMouseEvents
If you modify these files, you must restart your system before the changes take effect.
The following sections describe some examples of gestures.
The file AccessKeyMouseEvents can associate keyboard
shortcuts with assistive technologies. For example, the following line enables
you to press-and-hold Ctrl + S for one second
to start Gnopernicus
in speech and Braille mode:
<Control>s 1 1000 1000 srcore --login --disable-magnifier --enable-speech --enable-braille
You can assign similar keyboard combinations to start Gnopernicus
in magnifier mode only. For example, the following
line enables you to press-and-hold Ctrl + M
for one second to start Gnopernicus
in magnifier
mode:
<Control>m 1 1000 1000 srcore --login --enable-magnifier --disable-speech
The above lines must be displayed as single lines in the AccessKeyMouseEvents file without line breaks. The formatting of this guide might display the lines over two lines.
You can use button, key, or switch actions to start assistive technologies.
Since the primary input device for many GOK
users
is a switch or button, this is a good way to enable users to start GOK at login time.
To reduce the likelihood of starting an application unintentionally,
you can associate the gestures with multiple switch presses or minimum durations.
For example, the following line in the file AccessKeyMouseEvents starts GOK
in inverse scanning mode
when the user presses the switch that is defined as Switch 2 three times within
two seconds, for a minimum of 100 milliseconds for each press:
<Switch2>3 100 2000 gok --login --accessmethod=inversescanning --scan-action=switch1 --select-action=switch2
Users who use single switches may prefer to start GOK
in automatic scanning mode. The following line starts GOK
in automatic scanning mode when the user presses the switch on an alternative
access device for more than four seconds:
<Switch>1 4000 5000 gok --login --accessmethod=automaticscanning --scan-action=switch1 --select-action=switch1
For information about the GOK
operating modes,
see the online Help for GOK
.
The above lines must be displayed as single lines in the AccessKeyMouseEvents file without line breaks. The formatting of this guide might display the lines over two lines.
You can also define gestures that involve only the motion of a pointing device such as a mouse, or an alternative pointing device, such as a head pointer or trackball. The syntax of the gesture does not change depending on whether you are using a mouse or an alternative pointing device.
If the dwellmouselistener GtkModule is loaded, alternative pointing devices are temporarily latched to the core pointer. This means that if the user moves the alternative pointing device, the onscreen pointer moves.
The following line starts GOK
in dwell mode
when the user moves the onscreen pointer from inside the login dialog through
the top edge, back into the dialog through the top edge, out of the dialog
through the left edge, back into the dialog through the left edge, and similarly
through the bottom and right edges of the dialog in a cross pattern:
TTLLBBRR O 10000 gok --login --access-method=dwellselection --input-device=MOUSE[3]
Note that the --input-device parameter specified in the gesture must match the name of the user input device as specified in /etc/X11/XF86Config.
The above line must be displayed as a single line in the AccessKeyMouseEvents file without line breaks. The formatting of this guide might display the line over two lines.