Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mouseemu(8) [debian man page]

MOUSEEMU(8)						      System Manager's Manual						       MOUSEEMU(8)

NAME
mouseemu - Emulate mouse buttons and mouse wheel SYNOPSIS
mouseemu [options] DESCRIPTION
Mouseemu is a daemon to emulate mouse buttons on trackpads with only one button. It lets you: - emulate middle and right click - emulate mouse wheel - block trackpad while typing It was initially developed for Apple PowerBooks and iBooks, but it may be useful on other architectures as well. This program only works when booting a 2.6 kernel because it uses the new uinput interface to emulate the mouse. OPTIONS
-middle B2_MOD B2_KEY Modifier and key for the middle (second) mouse button. Defaults to F10 and no modifier on PowerPC and Intel Macs, and to none on all other architectures. -right B3_MOD B3_KEY Modifier and key for the right (third) mouse button. Defaults to F11 and no modifier on PowerPC and Intel Macs, and to none on all other architectures. -scroll SCROLL_MOD Modifier for the scrolling function. Defaults to Alt. -typing-block DELAY Time in milliseconds for which the trackpad will be blocked while typing on the keyboard. Defaults to 300ms. -device UINPUT Device node for the uinput device. Defaults to /dev/uinput. If this device is not read and writeable the following devices are also tried: /dev/uinput, /dev/input/uinput and /dev/misc/uinput. -nofork don't run in the background -autorescan Automatically scan every 5s for new devices. This is normally not need, as udev should inform mouseemu about new devices. -debug print debugging messages about device scans -help show usage message The key codes for the buttons and modifiers are key scancodes. They can be found in include/linux/input.h in the kernel headers or by using `showkey` in a console. The keycodes must be given as decimal values (`showkey` displays hex values!). Mouseemu does normally not automatically scan for new devices. An udev rule is used to trigger a rescan when new devices are connected. You can also trigger a rescan manually by sending a HUP signal to the mouseemu process. EXAMPLES
To have the same behaviour as in MacOS X (CTRL-click for right mouse button and no emulation for the middle button): mouseemu -middle 0 0 -right 29 272 The code for the (left) mouse button is 272 (0x110 in hex). The code for CTRL is 29. Trigger a rescan for newly attached devices: kill -HUP `cat /var/run/mouseemu.pid` AUTHOR
Mouseemu was written by Colin Leroy <colin@colino.net>. This manpage was originally written by Gaudenz Steinlin <gaudenz@debian.org> for the Debian Project, but may be used by others under the terms of the GNU General Public License. 2005-03-29 MOUSEEMU(8)

Check Out this Related Man Page

LIRCMD(8)						  System Administration Utilities						 LIRCMD(8)

NAME
lircmd - LIRC mouse daemon translates infrared signals into mouse events SYNOPSIS
lircmd [options] [config-file] DESCRIPTION
This daemon can simulate a MouseSystems, IntelliMouse or IMPS/2 type mouse. It gets the received buttons from lircd and converts them to mouse events. To make this possible, lircmd needs a config file located in /etc/lircmd.conf. In this file you have to determine which but- ton from which remote causes a mouse move or a mouse button click. You can also specify a special button which activates or deactivates the mouse mode. -h --help display this message -v --version display version -n --nodaemon don't fork to background -u --uinput generate Linux input events OPTIONS
If you provide the --nodaemon option lircmd won't fork to background. On Linux systems the --uinput option will enable automatic generation of Linux input events. lircmd will open /dev/input/uinput and inject the simulated mouse events into the Linux kernel rather than creating the /dev/lircm device. FILES
lircmd will use syslogd to output error messages. It depends on your system configuration where they will show up. DAEMONS
lircd and lircmd are daemons. You should start them in some init script depending on your system. There are some example scripts for dif- ferent distributions in the contrib directory. lircmd has to be started after lircd as it connects to the socket lircd provides. If you start lircd or lircmd from your shell prompt you will usually get back immediately to the prompt. Often people think that the pro- gram has died. But this is not an error. lircd and lircmd are daemons. Daemons always run in background. SEE ALSO
The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory. lircmd 0.9.0-pre1 October 2010 LIRCMD(8)
Man Page