Normally, button 1 generates a button 1 event, button 2 generates a button
2 event, and so forth.
To change the mouse button mapping, first find out how many mouse buttons are
configured by your X server:
$ xmodmap -pp
There are 5 pointer buttons defined.
Physical Button
Button Code
1 1
2 2
3 3
4 4
5 5
In normal operation, buttons 1??“3 correspond to the left, middle, and right mouse
buttons; button 4 and 5 are scrollwheel up and down; and buttons 6 and 7 are scrollwheel
left and right (for mice that have two scrollwheels, a tiltable scrollwheel, or
buttons on the side of the mouse and typically used for browser history navigation).
You can use the xmodmap pointer command to specify the button event code for
each physical button:
$ xmodmap -e "pointer = 1 10 11 4 5"
You must specify a code for each button defined on the mouse (five for this mouse).
In this example, button 1 (left button) and buttons 4 and 5 (scrollwheel up and
down) retain their original meaning, but button 2 will generate a button 10 event,
and button 3 will generate a button 11 event, both of which are ignored by most
applications. This effectively disables buttons 2 and 3.
15.6
224 Chapter 15: Building a Kiosk
If you are using xmodmap to change the keyboard, you can append the pointer line
to the end of the xmodmap input file:
pointer = 1 10 11 4 5
Some applications may not use the pointer mapping set by xmodmap and may continue
to recognize all of the mouse buttons.
Pages:
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343