Re: [AD] Fwd: fourth mouse button under windows

[Evert Glebbeek <eglebbk@xxxxxxxxxx>]

> My thoughts are simply that Allegro should provide information on all
> the buttons available, as long as it's trivial to do so. The first
> three buttons could be "special" in that they have helper macros, etc
> - as they are much more common. The docs could just simply state that
> macros or whatever aren't available for buttons > 3 and use them at
> your own risk.

Ok, patch commited. I've attached a minimalist patch for the documentation.

Evert

Index: docs/src/allegro._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/allegro._tx,v
retrieving revision 1.269
diff -u -r1.269 allegro._tx
--- docs/src/allegro._tx	18 Oct 2004 08:33:58 -0000	1.269
+++ docs/src/allegro._tx	20 Oct 2004 20:02:07 -0000
@@ -2290,7 +2290,8 @@
    the screen. The `mouse_z' variable holds the current wheel position, when 
    using an input driver that supports wheel mice. The `mouse_b' variable is 
    a bitfield indicating the state of each button: bit 0 is the left button, 
-   bit 1 the right, and bit 2 the middle button. For example:
+   bit 1 the right, and bit 2 the middle button. If there is a fourth button,
+   then bit 3 contains the status of this button. For example:
 <codeblock>
       if (mouse_b & 1)
 	 printf("Left button is pressed\n");
@@ -2419,7 +2420,8 @@
    call, which is a bitmask containing any of the values MOUSE_FLAG_MOVE, 
    MOUSE_FLAG_LEFT_DOWN, MOUSE_FLAG_LEFT_UP, MOUSE_FLAG_RIGHT_DOWN, 
    MOUSE_FLAG_RIGHT_UP, MOUSE_FLAG_MIDDLE_DOWN, MOUSE_FLAG_MIDDLE_UP, and 
-   MOUSE_FLAG_MOVE_Z.
+   MOUSE_FLAG_MOVE_Z. Note that even if the mouse has more than three buttons,
+   only the first three can be trapped using a callback.