* Code cleanup:

[u-boot.git] / board / MAI / bios_emulator / scitech / include / event.h

diff --git a/board/MAI/bios_emulator/scitech/include/event.h b/board/MAI/bios_emulator/scitech/include/event.h
index 0de45172d6ee9808d4a89b8be338da548312b533..beeac87645e54ad66b93ca09e2fa42d504859e2b 100644 (file)
--- a/board/MAI/bios_emulator/scitech/include/event.h
+++ b/board/MAI/bios_emulator/scitech/include/event.h
@@ -201,9 +201,9 @@ keyboard), but the translated ASCII values may be different depending on
 the country code pages in use.
 
 NOTE:   Scan codes in the event library are not really hardware scan codes,
-        but rather virtual scan codes as generated by a low level keyboard
-        interface driver. All virtual codes begin with scan code 0x60 and
-        range up from there.
+       but rather virtual scan codes as generated by a low level keyboard
+       interface driver. All virtual codes begin with scan code 0x60 and
+       range up from there.
 
 HEADER:
 event.h
@@ -496,38 +496,38 @@ event.h
 
 MEMBERS:
 which       - Window identifier for message for use by high level window manager
-              code (i.e. MegaVision GUI or Windows API).
+             code (i.e. MegaVision GUI or Windows API).
 what        - Type of event that occurred. Will be one of the values defined by
-              the EVT_eventType enumeration.
+             the EVT_eventType enumeration.
 when        - Time that the event occurred in milliseconds since startup
 where_x     - X coordinate of the mouse cursor location at the time of the event
-              (in screen coordinates). For joystick events this represents
-              the position of the first joystick X axis.
+             (in screen coordinates). For joystick events this represents
+             the position of the first joystick X axis.
 where_y     - Y coordinate of the mouse cursor location at the time of the event
-              (in screen coordinates). For joystick events this represents
-              the position of the first joystick Y axis.
+             (in screen coordinates). For joystick events this represents
+             the position of the first joystick Y axis.
 relative_x  - Relative movement of the mouse cursor in the X direction (in
-              units of mickeys, or 1/200th of an inch). For joystick events
-              this represents the position of the second joystick X axis.
+             units of mickeys, or 1/200th of an inch). For joystick events
+             this represents the position of the second joystick X axis.
 relative_y  - Relative movement of the mouse cursor in the Y direction (in
-              units of mickeys, or 1/200th of an inch). For joystick events
-              this represents the position of the second joystick Y axis.
+             units of mickeys, or 1/200th of an inch). For joystick events
+             this represents the position of the second joystick Y axis.
 message     - Event specific message for the event. For use events this can be
-              any user specific information. For keyboard events this contains
-              the ASCII code in bits 0-7, the keyboard scan code in bits 8-15 and
-              the character repeat count in bits 16-30. You can use the
-              EVT_asciiCode, EVT_scanCode and EVT_repeatCount macros to extract
-              this information from the message field. For mouse events this
-              contains information about which button was pressed, and will be a
-              combination of the flags defined by the EVT_eventMouseMaskType
-              enumeration. For joystick events, this conatins information
-              about which buttons were pressed, and will be a combination of
-              the flags defined by the EVT_eventJoyMaskType enumeration.
+             any user specific information. For keyboard events this contains
+             the ASCII code in bits 0-7, the keyboard scan code in bits 8-15 and
+             the character repeat count in bits 16-30. You can use the
+             EVT_asciiCode, EVT_scanCode and EVT_repeatCount macros to extract
+             this information from the message field. For mouse events this
+             contains information about which button was pressed, and will be a
+             combination of the flags defined by the EVT_eventMouseMaskType
+             enumeration. For joystick events, this conatins information
+             about which buttons were pressed, and will be a combination of
+             the flags defined by the EVT_eventJoyMaskType enumeration.
 modifiers   - Contains additional information about the state of the keyboard
-              shift modifiers (Ctrl, Alt and Shift keys) when the event
-              occurred. For mouse events it will also contain the state of
-              the mouse buttons. Will be a combination of the values defined
-              by the EVT_eventModMaskType enumeration.
+             shift modifiers (Ctrl, Alt and Shift keys) when the event
+             occurred. For mouse events it will also contain the state of
+             the mouse buttons. Will be a combination of the values defined
+             by the EVT_eventModMaskType enumeration.
 next        - Internal use; do not use.
 prev        - Internal use; do not use.
 ****************************************************************************/
@@ -555,8 +555,8 @@ different code page translation table if you want to support keyboards
 other than the US English keyboard (the default).
 
 NOTE:   Entries in code page tables *must* be in ascending order for the
-        scan codes as we do a binary search on the tables for the ASCII
-        code equivalents.
+       scan codes as we do a binary search on the tables for the ASCII
+       code equivalents.
 
 HEADER:
 event.h