diff options
Diffstat (limited to 'jsmond.rst')
-rw-r--r-- | jsmond.rst | 24 |
1 files changed, 19 insertions, 5 deletions
@@ -20,7 +20,7 @@ deactivate screensaver on joystick activity SYNOPSIS ======== -jsmond [**-i interval**] [**-k keycode** | **-b button**] [**-d dir**] [**-j name**] [**-D**] [**joydev [joydev ...]**] +jsmond [**-i interval**] [**-m** | **-k keycode** | **-b button**] [**-d dir**] [**-j name**] [**-D**] [**joydev [joydev ...]**] DESCRIPTION =========== @@ -35,7 +35,7 @@ as joysticks are plugged in and unplugged. Every *interval* milliseconds (250, or whatever **-i** is set to), jsmond checks to see if there's been any activity on any of the devices it's -monitoring. If so, it sends a fake keystroke or mouse button click, which +monitoring. If so, it sends a fake mouse movement, keystroke, or mouse button click, which the screen saver will see as activity. It's recommended to let jsmond find the joysticks itself. However, @@ -63,7 +63,14 @@ OPTIONS -b <button> Send a click of this button when activity is detected, rather than a keystroke. Should be a button that - applications don't normally respond to (6 or higher). + applications don't normally respond to (6 or higher), + but in some environments, the window manager responds to + all the 'extra' buttons as though they were button 1. + +-m Send mouse movements rather than a keystroke. This will + move the pointer 10 pixels to the right and down, then + 10 pixels to the left and up, then warp the pointer back + to its starting point. These options are intended for developers and *really* shouldn't be needed for normal use: @@ -100,9 +107,13 @@ jsmond will wait for devices to come into existence (e.g. as created by **udev**). If the screensaver is configured to lock the screen, and it has already -activated, pressing a joystick button/direction will just bring up the +done so, pressing a joystick button/direction will just bring up the password dialog, same as pressing a key or mouse button would. +jsmond depends on the XTest extension being present in the X server. If +you get a "X server doesn't support XTest extension" error, see your X +server documentation to find out how to enable XTest. + EXIT STATUS =========== @@ -124,7 +135,10 @@ names (better to autodetect). Normally once daemonized, jsmond is very robust. However, if something does go wrong, there's no way to find out what. Probably there should -be a log file, or use syslog. +be a log file, or use syslog (or is that overkill?). + +It should be (but currently isn't) possible to at least work in +mouse-motion mode even without the XTest extension, via XWarpPointer(). jsmond isn't portable. It only works on Linux, at least for now, for three reasons: |