Key Scripter 1.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Key Scripter 1.4 (Default branch)
# 1  
Old 05-06-2008
Key Scripter 1.4 (Default branch)

Key Scripter listens to key press/release events from a keyboard or a mouse and sends fake key events to an X display. It supports gaming keypads such as the Nostromo SpeedPad and allows the creation and usage of complicated key scripts for games and other applications. License: GNU General Public License v3 Changes:
This release contains a couple of minor bugfixes and an improved example configuration. The development status of Key Scripter is now stable.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Begining Shell scripter

I am trying to write for my class project a shell script, using bourne shell, that will take one command, either -l or -w. If -l is entered then the script should output the names of all the files in my working directory sorted in increasing order of the number of lines in the file. If -w is input... (2 Replies)
Discussion started by: C.Ronaldo-7-
2 Replies

2. Shell Programming and Scripting

new scripter

Hello all, new to scripting (and unix!) here. Im trying to write a script for something i have to do for work and for some reason it just isnt working. im using the ksh. Can someone please tell me why $PRODUCT=$1 CONFIG=./etc/$PRODUCT_config.xml print Using $CONFIG prints... (1 Reply)
Discussion started by: Gwoodhouse0
1 Replies
Login or Register to Ask a Question
WSMUX(4)						   BSD Kernel Interfaces Manual 						  WSMUX(4)

NAME
wsmux -- console keyboard/mouse multiplexor for wscons SYNOPSIS
wskbd* at ... mux 1 wsmouse* at ... mux 0 pseudo-device wsmux DESCRIPTION
The wsmux is a pseudo-device driver that allows several wscons(4) input devices to have their events multiplexed into one stream. The typical usage for this device is to have two multiplexors, one for mouse events and one for keyboard events. All wsmouse(4) devices should direct their events to the mouse mux (normally 0) and all keyboard devices, except the console, should direct their events to the key- board mux (normally 1). A device will send its events to the mux indicated by the mux locator. If none is given the device will not use a multiplexor. The keyboard multiplexor should be connected to the display, using the wsconscfg(8) command. It will then receive all key- strokes from all keyboards and, furthermore, keyboards can be dynamically attached and detached without further user interaction. In a simi- lar way, the window system will open the mouse multiplexor and receive all mouse events; mice can also be dynamically attached and detached. If a wskbd(4) or wsmouse(4) device is opened despite having a mux it will be detached from the mux. It is also possible to inject events into a multiplexor from a user program. FILES
For each mux device, /dev/wsmuxN there is a control device /dev/wsmuxctlN. The control device has a minor number 128 greater than the regu- lar mux device. It can be used to control the mux even when it is open, e.g., by wsmuxctl(8). /dev/wsmouse a.k.a. /dev/wsmux0 /dev/wskbd a.k.a. /dev/wsmux1 /usr/include/dev/wscons/wsconsio.h SEE ALSO
wscons(4), wsdisplay(4), wskbd(4), wsmouse(4), moused(8), wsconscfg(8), wsconsctl(8), wsfontload(8), wsmoused(8), wsmuxctl(8) BSD
July 26, 1999 BSD