Mouse

mouse driver (QNX)

Syntax:

Mouse [-b [-i interrupt][-p address]] [-g number] 
      [-n name] [-s baud] [-x] [-y] type
      [<serial_port] &

Mouse query

Mouse [-n name] test

Options:

-b: Assume a bus mouse (default is serial).
-g number: The gain to apply to mouse motions (default is 1).
-i interrupt: The hardware interrupt to use for the bus mouse (default is 5).
-p address: The I/O address of the bus mouse, in hex (default is 23C).
query: List all supported mouse protocols and default parameters.
-n name: The name to register (default is /dev/mouse) or the name of an installed driver to test.
-s baud: Set the serial port to this baud rate (default is 1200 baud).
test: Test the installed mouse driver.
-x: Reverse x-axis motions.
-y: Reverse y-axis motions.
type: The type of mouse (see Description).
<serial_port: The device associated with the standard input specifies the port your serial mouse is attached to. From the shell, this can be accomplished using the shell < redirection operator.

Examples:

Assume a Microsoft Serial Mouse on /dev/ser1:

    Mouse msoft </dev/ser1 &

Assume a standard bus mouse:

    Mouse -b msoft &

Test an installed mouse driver:

    Mouse test

Description:

The Mouse driver manages the mouse on a QNX system. It accepts and interprets the stream of data generated by a moving mouse, and processes this into an internal first-in first-out queue of significant mouse events. Application programs can "read" these mouse events by sending messages to the Mouse server via a set of mouse-specific functions.

To minimize buffer requirements, yet ensure a consistent mouse position, Mouse "compresses" unread mouse motions. A mouse event is always generated when the user presses or releases a mouse button.

To ensure that mouse motions apply only to the visible console, and don't interfere with background programs, Mouse tracks the system console and flushes all mouse events if the visible console is changed.

To start or terminate Mouse, you must be logged in as the superuser (root).

At the time of printing, the following mouse types are supported:

type	description
`ati`	ATI mouse port (picks either `atiold` or `atinew` automatically)
`atinew`	ATI Graphics ULTRA, ATI Graphics Vantage
`atiold`	ATI Wonder mouse port
`fulcrum`	Fulcrum Trackball Plus
`inport`	Microsoft, post 1986
`logit`	Logitech C7 Series Mouse, Logitech C9 Series Mouse
`mman`	Logitech MouseMan Serial Mouse
`msoft`	Standard 200 DPI Microsoft Mouse
`msys`	Mouse Systems Mouse
`ps2`	IBM PS/2 Integrated Mouse

To see a list of currently supported mouse types, simply type:

    use Mouse

    Mouse query

Exit status:

For Mouse ... type ... & :

When run as a driver, Mouse will usually never terminate. However, it will terminate if errors are encountered during initialization or in response to being given bad command-line parameters. Also, Mouse will terminate if it has forked itself into the background (which it will attempt to do if it was not started in the background to begin with).

0: Mouse successfully forked a background copy of itself.
>0: An error occurred during initialization, or an attempt to fork a copy of itself into the background failed. A diagnostic message will have been written to the standard error.

For Mouse query :

In the query mode, Mouse will always exit with a status of 0.

For Mouse test :

0: User successfully terminated a test by pressing both left and right mouse buttons.
>0: User had to terminate the test by killing the Mouse test process, or Mouse was unable to start the test because the Mouse driver was not running.

Files:

For Mouse ... type ... &:

When run as a driver, Mouse will usually close both standard output and standard error after startup initializations have been completed. During initialization, warning/informative messages may be written to standard output. Any problem which will cause Mouse to terminate will cause a diagnostic message to be written to standard error.

If the mouse type is a form of serial mouse, the standard input must be directed from the block special device representing the serial port to which the mouse is attached. (Thus the Dev.ser driver must be running.) If the mouse type is a bus mouse, Mouse will close its standard input.

Mouse will adopt a special file in the pathname prefix tree through which other programs can communicate with the mouse. This file is usually /dev/mouse, but may be something else if the -n option is used.

For Mouse query:

The results of a Mouse query are written to the standard output.

For Mouse test:

in the test mode, Mouse will attempt to talk to the mouse driver attached to the filename specified by the -n or to /dev/mouse.

Test output will be written to standard output.