2 files changed, 40 insertions, 13 deletions

diff --git a/doc/asciidoc/fluxbox-keys.txt b/doc/asciidoc/fluxbox-keys.txt
index ed69a57..3f3431d 100644
--- a/doc/asciidoc/fluxbox-keys.txt
+++ b/doc/asciidoc/fluxbox-keys.txt
@@ -55,7 +55,7 @@ are most commonly used:
 where *Mod1* is the Alt key on the PC keyboard and *Mod4* is usually a key
 branded with a familiar company logo.
 
-There are also some special modifiers that refer to mouse button presses:::
+There are also some special modifiers that refer to mouse button events:::
 *OnDesktop*;;
         The mouse cursor is over the desktop (root window), and not any
         window.
@@ -84,13 +84,21 @@ the key, and see the name in the output. If you have some "special" keys that
 do not produce a key name in the output of *xev(1)*, you can just use the
 keycode (NOT the keysym!) in your keys file.
 
-Commands can also be bound to mouse button presses, for which the proper "key"
-name is *Mouse*'n' where 'n' is the number of the mouse button. For example,
-*Mouse1* is the primary button, and *Mouse4* / *Mouse5* are the scroll wheel
-events, in normal configurations. *xev(1)* can also be used to tell the button
-number.
+Commands can also be bound to mouse events ('N' denotes the number of the
+button, eg. '1' is the primary button, '4'/'5' are the wheel buttons):
+
+*MouseN*;;
+        The mouse button 'N' is pressed down and holded.
+*ClickN*;;
+        The mouse button 'N' is clicked (pressed and released with no
+        movement in between)
+*MoveN*;;
+        The mouse button 'N' is currently holded, the binded action is triggered
+        as often as the mouse moves.
+
+
+There are some special "keys" that let you bind events to non-keyboard events:
 
-There are some special "keys" that let you bind events to non-keyboard events:::
 *ChangeWorkspace*;;
         Fires when the workspace changes. This can be used to change backgrounds or
         do anything else you like when you switch to a new workspace. See the
diff --git a/doc/fluxbox-keys.5.in b/doc/fluxbox-keys.5.in
index 6e641f9..2b29891 100644
--- a/doc/fluxbox-keys.5.in
+++ b/doc/fluxbox-keys.5.in
@@ -2,12 +2,12 @@
 .\"     Title: fluxbox-keys
 .\"    Author: [see the "AUTHORS" section]
 .\" Generator: DocBook XSL Stylesheets v1.75.1 <http://docbook.sf.net/>
-.\"      Date: 12/14/2009
+.\"      Date: 12/17/2009
 .\"    Manual: Fluxbox Manual
 .\"    Source: fluxbox-keys.txt
 .\"  Language: English
 .\"
-.TH "FLUXBOX\-KEYS" "5" "12/14/2009" "fluxbox\-keys\&.txt" "Fluxbox Manual"
+.TH "FLUXBOX\-KEYS" "5" "12/17/2009" "fluxbox\-keys\&.txt" "Fluxbox Manual"
 .\" -----------------------------------------------------------------
 .\" * set default formatting
 .\" -----------------------------------------------------------------
@@ -53,7 +53,7 @@ You can get a list of possible modifiers by calling \(oqxmodmap \-pm\(cq\&. This
 .sp
 where \fBMod1\fR is the Alt key on the PC keyboard and \fBMod4\fR is usually a key branded with a familiar company logo\&.
 .PP
-There are also some special modifiers that refer to mouse button presses
+There are also some special modifiers that refer to mouse button events
 .RS 4
 .PP
 \fBOnDesktop\fR
@@ -90,10 +90,30 @@ You may specify a key by its key name (for example, \fBa\fR or \fBspace\fR) or b
 .sp
 If you don\(cqt know the name of a key, you can run \fBxev(1)\fR in a terminal, push the key, and see the name in the output\&. If you have some "special" keys that do not produce a key name in the output of \fBxev(1)\fR, you can just use the keycode (NOT the keysym!) in your keys file\&.
 .sp
-Commands can also be bound to mouse button presses, for which the proper "key" name is \fBMouse\fR\fIn\fR where \fIn\fR is the number of the mouse button\&. For example, \fBMouse1\fR is the primary button, and \fBMouse4\fR / \fBMouse5\fR are the scroll wheel events, in normal configurations\&. \fBxev(1)\fR can also be used to tell the button number\&.
+Commands can also be bound to mouse events (\fIN\fR denotes the number of the button, eg\&. \fI1\fR is the primary button, \fI4\fR/\fI5\fR are the wheel buttons):
 .PP
-There are some special "keys" that let you bind events to non\-keyboard events
+\fBMouseN\fR
 .RS 4
+The mouse button
+\fIN\fR
+is pressed down and holded\&.
+.RE
+.PP
+\fBClickN\fR
+.RS 4
+The mouse button
+\fIN\fR
+is clicked (pressed and released with no movement in between)
+.RE
+.PP
+\fBMoveN\fR
+.RS 4
+The mouse button
+\fIN\fR
+is currently holded, the binded action is triggered as often as the mouse moves\&.
+.RE
+.sp
+There are some special "keys" that let you bind events to non\-keyboard events:
 .PP
 \fBChangeWorkspace\fR
 .RS 4
@@ -101,7 +121,6 @@ Fires when the workspace changes\&. This can be used to change backgrounds or do
 \fBEXAMPLES\fR
 below for one idea\&.
 .RE
-.RE
 .if n \{\
 .sp
 .\}