MOUSED(8) | System Manager's Manual | MOUSED(8) |
moused
— pass
mouse data to mouse mux
moused |
[-DPRacdfs ] [-I
file] [-F
rate] [-r
resolution] [-S
baudrate] [-W
devicename] [-a
X[,Y]] [-m
N=M] [-w
N] [-z
target] [-t
mousetype] [-3
[-E timeout]]
-p port |
moused |
[-Pd ] -p
port -i
info |
The mouse daemon moused
and the console
driver work together to support access to serial mice from user programs.
They virtualize the mouse and provide user programs with mouse data in the
standard format (see
wsmouse(4)).
moused
listens to the specified port for
mouse data, interprets and then passes it via ioctls to the console driver.
It reports translation movement, button press/release events and movement of
the roller or the wheel if available. The roller/wheel movement is reported
as “Z” axis movement.
If moused
receives the signal
SIGHUP
, it will reopen the mouse port and
reinitializes itself. Useful if the mouse is attached/detached while the
system is suspended.
The following options are available:
-3
-D
-E
timeoutmoused
waits timeout
milliseconds at most before deciding whether two buttons are being pressed
simultaneously. The default timeout is 100 milliseconds.-F
rate-I
filemoused
in the specified
file. Without this option, the process id will be stored in
/var/run/moused.pid.-P
-i
option, moused
will not
be able to print useful information for the serial mouse.-R
-t
option below. It is often used with the
-D
option above. Both RTS and DTR lines may need
to be dropped for a 3-button mouse to operate in the
mousesystems mode.-S
baudrate-W
devicename-a
X[,Y]-c
-d
-f
-i
info-t
option below.moused
may not always be able to
identify the model.If moused
cannot determine the
requested information, it prints ``unknown'' or ``generic''.
-m
N=M-p
port-r
resolution-s
-t
typemoused
automatically select an appropriate
protocol for the given mouse. If you entirely omit this option on the
command line, -t
auto is
assumed. Under normal circumstances, you need to use this option only if
moused
is not able to detect the protocol
automatically.
Note that if a protocol type is specified with this option,
the -P
option above is implied and Plug and Play
COM device enumeration procedure will be disabled.
Valid types for this option are listed below.
For the serial mouse:
-w
N-z
option below.-z
targetThe motion of the second wheel will be mapped to the buttons N3, for the negative direction, and N4, for the positive direction. If the buttons N3 and N4 actually exist in this mouse, their actions will not be detected.
Note that horizontal movement or second roller/wheel movement may not always be detected, because there appears to be no accepted standard as to how it is encoded.
Note also that some mice think left is the negative horizontal direction, others may think otherwise. Moreover, there are some mice whose two wheels are both mounted vertically, and the direction of the second vertical wheel does not match the first one's.
As many instances of moused
as the number
of mice attached to the system may be run simultaneously; one instance for
each serial mouse.
moused
moused -p /dev/tty00 -i
type
Let moused
determine the protocol type of
the mouse at the serial port /dev/tty00. If
successful, moused
will print the type, otherwise it
will say ``unknown''.
moused -p /dev/tty00
If moused
is able to identify the protocol
type of the mouse at the specified port automatically, you can start the
daemon without the -t
option and enable the mouse
pointer in the text console as above.
moused -p /dev/tty01 -t
microsoft
Start moused
on the serial port
/dev/tty01. The protocol type
microsoft is explicitly specified by the
-t
option.
moused -p /dev/tty01 -m 1=3 -m
3=1
Assign the physical button 3 (right button) to the logical button 1 (logical left) and the physical button 1 (left) to the logical button 3 (logical right). This will effectively swap the left and right buttons.
moused -p /dev/tty01 -t intellimouse
-z 4
Report negative Z axis (roller) movement as the button 4 pressed and positive Z axis movement as the button 5 pressed.
The mouse daemon is normally enabled by setting moused=YES in /etc/rc.conf.
moused
partially supports “Plug and
Play External COM Device Specification” in order to support PnP
serial mice. However, due to various degrees of conformance to the
specification by existing serial mice, it does not strictly follow version
1.0 of the standard. Even with this less strict approach, it may not always
determine an appropriate protocol type for the given serial mouse.
The mouse daemon moused
first appeared in
FreeBSD 2.2 and NetBSD
1.6.
moused
was written by
⟨msmith@FreeBSD.org⟩. This manual page was written by
Mike Pritchard ⟨mpp@FreeBSD.org⟩. The
daemon and manual page have since been updated by Kazutaka
Yokota ⟨yokota@FreeBSD.org⟩. The
NetBSD port was done by Lennart
Augustsson ⟨augustss@NetBSD.org⟩.
Many pad devices behave as if the first (left) button were pressed if the user `taps' the surface of the pad. In contrast, some ALPS GlidePoint and Interlink VersaPad models treat the tapping action as fourth button events. Use the option ``-m 1=4'' for these models to obtain the same effect as the other pad devices.
October 29, 2001 | NetBSD 10.99 |