Free input event software for linux

Swinput can fake a mouse and a keyboard by using the Linux Input System. The swinput modules read from a device and fakes hardware event (mouse motion, key presses etc) as commands written on the devices. Swinput presents status etc on the proc filesystem.

Swinput project is useful when testing applications.

It was developed to use when testing Xnee.

Event is an Event loop processing.

SYNOPSIS

use Event qw(loop unloop);

# initialize application
Event->flavor(attribute => value, ...);

my $ret = loop();

# and some callback will call
unloop(ok);

The Event module provide a central facility to watch for various types of events and invoke a callback when these events occur. The idea is to delay the handling of events so that they may be dispatched in priority order when it is safe for callbacks to execute.

Events (in the ordinary sense of the word) are detected by watchers, which reify them as events (in the special Event module sense). For clarity, the former type of events may be called "source events", and the latter "target events". Source events, such as signals arriving, happen whether or not they are being watched. If a source event occurs which a watcher is actively watching then the watcher generates a corresponding target event. Target events are only created by watchers. If several watchers are interested in the same source event then each will generate their own target event. Hence, any particular source event may result in zero, one, two, or any number of target events: the same as the number of watchers which were actively watching for it.

Target events are queued to be processed in priority order (priority being determined by the creating watcher) and in FIFO order among events of the same priority. Queued ("pending") events can, in some cases, be cancelled before being processed. A queued event is processed by being passed to the callback function (or method on a particular object or class) which was specified to the watcher.

A watcher, once created, operates autonomously without the Event user having to retain any reference to it. However, keeping a reference makes it possible to modify most of the watchers characteristics. A watcher can be switched between active and inactive states. When inactive, it does not generate target events.

Some types of source event are not reified as target events immediately. Signals received, for example, are counted initially. The counted signals are reified at certain execution points. Hence, signal events may be processed out of order, and if handled carelessly, on the wrong side of a state change in event handling. A useful way to view this is that occurrence of the source event is not actually the arrival of the signal but is triggered by the counting of the signal.
Reification can be forced when necessary. The schedule on which some other events are created is non-obvious. This is especially the case with watchers that watch for a condition rather than an event. In some cases, target events are generated on a schedule that depends on the operation of the event loop.

OpenInput project is a cross-platform, easy-to-use, portable input handler library, written in C.
The primary goal of OpenInput is to make it easier for application programmers to write portable code that deals with input from mice, keyboards, joysticks and other devices.
In other words, OpenInput will allow you to write a single piece of code that handles input for your application for all platforms, for example GNU/Linux, Windows and MacOS X.
This is achieved by abstracting the low-level platform-specific input device handling into a stable, intuitive, platform-independent API: OpenInput.
Main features:
- Total platform independence
- Easy to use, sane and simple API
- Fully documented functions and data structures
- Automatic configuration of available devices
- Generic event handling
- Keyboard state managment (eg. up/down/lock)
- Mouse motion and state managment (eg. movement, buttons up/down)
- Joystick motion and state handling for axes, hats and trackballs
- Can "hook" into existing windows
- Provides resize, iconify, close and expose events for the application window
- Action mapping, so events can be handled without any knowledge of the underlying device
- Pointer (mouse) grabbing inside window
- Show/hide pointer inside window
- Keyboard focus grabbing
Enhancements:
- This version contains major documentation updates, both big and small bugfixes, and minor feature enhancements which dont break the API.

Tk::event contains miscellaneous event facilities: define virtual events and generate events.

SYNOPSIS

$widget->eventAction(?arg, arg, ...?);

The eventAction methods provides several facilities for dealing with window system events, such as defining virtual events and synthesizing events. Virtual events are shared by all widgets of the same MainWindow. Different MainWindows can have different virtual event.

The following methods are currently supported:

$widget->eventAdd(, sequence ?,sequence, ...?)

Associates the virtual event virtual with the physical event sequence(s) given by the sequence arguments, so that the virtual event will trigger whenever any one of the sequences occurs. Virtual may be any string value and sequence may have any of the values allowed for the sequence argument to the bind method. If virtual is already defined, the new physical event sequences add to the existing sequences for the event.

$widget->eventDelete( ?,sequence, sequence, ...?)

Deletes each of the sequences from those associated with the virtual event given by virtual. Virtual may be any string value and sequence may have any of the values allowed for the sequence argument to the bind method. Any sequences not currently associated with virtual are ignored. If no sequence argument is provided, all physical event sequences are removed for virtual, so that the virtual event will not trigger anymore.

$widget->eventGenerate(event ?,option => value, option => value, ...?)

Generates a window event and arranges for it to be processed just as if it had come from the window system. $window is a reference to the window for which the event will be generated. Event provides a basic description of the event, such as < Shift-Button-2 > or >. If Window is empty the whole screen is meant, and coordinates are relative to the screen. Event may have any of the forms allowed for the sequence argument of the bind method except that it must consist of a single event pattern, not a sequence. Option-value pairs may be used to specify additional attributes of the event, such as the x and y mouse position; see "EVENT FIELDS" below. If the -when option is not specified, the event is processed immediately: all of the handlers for the event will complete before the eventGenerate method returns. If the -when option is specified then it determines when the event is processed.

$widget->eventInfo(?>?)

Returns information about virtual events. If the argument is omitted, the return value is a list of all the virtual events that are currently defined. If is specified then the return value is a list whose elements are the physical event sequences currently defined for the given virtual event; if the virtual event is not defined then undef is returned.

Event::RPC is a event based transparent Client/Server RPC framework.

SYNOPSIS

#-- Server Code
use Event::RPC::Server;
use My::TestModule;
my $server = Event::RPC::Server->new (
port => 5555,
classes => { "My::TestModule" => { ... } },
);
$server->start;

----------------------------------------------------------

#-- Client Code
use Event::RPC::Client;
my $client = Event::RPC::Client->new (
server => "localhost",
port => 5555,
);
$client->connect;

#-- Call methods of My::TestModule on the server
my $obj = My::TestModule->new ( foo => "bar" );
my $foo = $obj->get_foo;

ABSTRACT

Event::RPC supports you in developing Event based networking client/server applications with transparent object/method access from the client to the server. Network communication is optionally encrypted using IO::Socket::SSL. Several event loop managers are supported due to an extensible API. Currently Event and Glib are implemented.

Event::Stats is a Perl module for event loop statistics. Instrument the Event module in order to gather statistics.

API

collect($yes)

Determines whether statistics are collected. Arithmetically adds $yes to the usage count. Stats are enabled while the usage count is positive.

$round_sec = round_seconds($sec)

Statistics are not collected in one second intervals. This function converts a *desired* time interval into an *available* time interval. Units are in seconds.

$elapse = total_time($sec)

Due to long-running callbacks, measurement intervals may take longer than expected. This function returns the actual clock-time for a given measurement interval.

($rans, $dies, $elapse) = idle_time($sec)

($runs, $dies, $elapse) = $watcher->stats($sec)

Return statistics for the last $sec seconds of operation. Three numbers are returned: the number of times the callback has been invoked, the number of uncaught exceptions and the number of seconds spent within the callback. Also see NetServer::ProcessTop.

enforce_max_callback_time($yes)

Useful for debugging. XXX

POE::Loop::Event is a bridge that supports Gtks event loop from POE.

SYNOPSIS

See POE::Loop.

This class is an implementation of the abstract POE::Loop interface. It follows POE::Loops public interface exactly. Therefore, please see POE::Loop for its documentation.

GNU CD Input and Control Library (libcdio) encapsulates CD-ROM reading and control. The libcdio package contains a library which encapsulates CD-ROM reading and control. Applications wishing to be oblivious of the OS- and device-dependent properties of a CD-ROM can use this library.
Some support for on-disk CD-image types like CDRWINs BIN/CUE format, cdrdaos TOC format, and Neros NRG format is available. Therefore, applications that use this library also have the ability to read on-disk CD images as though they were CDs.
A library for working with ISO-9660 filesystems (libiso9660) is included. A generic interface for issuing MMC (multimedia commands) is also part of the libcdio library.
The cdparanoia library and cdparanoia command are included making this the only single-source cdparanoia that works on FreeBSD, cygwin, Solaris, BSDI as well as GNU/Linux.
Some uses of the library:
- Video CD authoring and ripping tools VCDImager
- VCD and/or CD-DA plugins for media players:
xine
videolans vlc.
gmerlin.
mplayerxp.
- kiso, a KDE GUI for creating, extracting and editing ISO 9660 images
- a Samba vfs module that that allows exporting a CD without mounting it
Utility programs in the libcdio package are:
cd-info
a program which displays CD information: number of tracks, CD-format and if possible basic information about the format. If libcddb is available, the cd-info program will display CDDB matches on CD-DA discs. And if a new enough version of libvcdinfo is available (from the vcdimager project), then cd-info shows basic VCD information.
cd-drive
a program which decribes CD-ROM/DVD drive characteristics
cd-paranoia
a program for extracting audio from a CD in a jitter- and error-tolerant way.
cd-read
a program for performing low-level block reading of a CD or CD image
cdda-player
a curses program using the audio controls to play a CD-DA through the audio output port.
iso-info
a program for displaying ISO-9660 information from an ISO-9660 image
iso-read
a program for extracting files from an ISO-9660 image.
Enhancements:
- A minor compilation problem was fixed.