RCU - Remote Control Unit Interface
This module provides a generic interface to remote control units (only receivers at the moment, as I cannot test more). It only provides an abstract management interface, other modules are required for the hardware access (RCU::Irman and RCU::Lirc are included, however).
Please read RCU::Receipts to get some idea on how to proceed after you installed the module (testing & standard techniques).
The RCU class provides a general interface to anything you might want to do to, it represents your application.
Creates a new RCU application.
interface must be an interface
specification similar to DBI's DSN:
low-level interface (without
RCU:: prefix) or an arrayref containing
name and constructor arguments. If the interface name has a
it will be used as-is (without that prefix, of course).
For a much better interface, see RCU::Event.
Return the RCU::Interface object used by this RCU object.
Simplified interface to the RCU (See also RCU::Event), return a cooked
keycode and a repeat count (initial keypress = 0, increasing while the
key is pressed). If
get is called in scalar context it only returns
This interface is problematic: no key-up events are generated, and the repeat events occur pseudo-randomly and have no time relation between each other, so better use the event-based interface provided by RCU::Event.
This class collects information about rcu keys.
RCU::Interface provides the base class for all rcu interfaces, it is rarely used directly.
Wait until a RCU event happens and return it. If the device can translate raw keys events (e.g. hex key codes) into meaningful names ("cooked" keys) it will return the cooked name as second value, otherwise both return values are identical.
get always returns an event, waiting if neccessary, while
checks for an event: If one is pending it is returned, otherwise
This perl extension was written by Marc Lehmann <firstname.lastname@example.org>.
No send interface.