Open Lighting Architecture  0.9.6
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Groups Pages
Public Member Functions | List of all members
ola::plugin::usbdmx::JaRuleWidget Class Reference

Detailed Description

Represents a Ja Rule hardware widget.

Inheritance diagram for ola::plugin::usbdmx::JaRuleWidget:
Inheritance graph
[legend]
Collaboration diagram for ola::plugin::usbdmx::JaRuleWidget:
Collaboration graph
[legend]

Public Member Functions

 JaRuleWidget (ola::io::SelectServerInterface *ss, AsyncronousLibUsbAdaptor *adaptor, libusb_device *device, const ola::rdm::UID &controller_uid)
 Create a new Ja Rule widget.
bool Init ()
 Initialize the widget.
void SendRDMRequest (ola::rdm::RDMRequest *request, ola::rdm::RDMCallback *on_complete)
 Send a RDM command.
void RunFullDiscovery (ola::rdm::RDMDiscoveryCallback *callback)
 Start a full discovery operation.
void RunIncrementalDiscovery (ola::rdm::RDMDiscoveryCallback *callback)
 Start an incremental discovery operation.
bool SendDMX (const DmxBuffer &buffer)
 Send DMX data from this widget.
void ResetDevice ()
 Send a reset message to the hardware widget.

Constructor & Destructor Documentation

ola::plugin::usbdmx::JaRuleWidget::JaRuleWidget ( ola::io::SelectServerInterface ss,
AsyncronousLibUsbAdaptor adaptor,
libusb_device *  device,
const ola::rdm::UID controller_uid 
)

Create a new Ja Rule widget.

Parameters
ssThe SelectServer to run the RDM callbacks on.
adaptorThe LibUsbAdaptor to use.
devicethe libusb_device for the Ja Rule widget.
controller_uidThe UID of the controller. This is used for DUB & Mute / Unmute messages.

TODO(simon): Can we instead read the UID from the hardware device itself?

Member Function Documentation

bool ola::plugin::usbdmx::JaRuleWidget::Init ( )
virtual

Initialize the widget.

Returns
true if this widget was initialized correctly, false otherwise.

Implements ola::plugin::usbdmx::Widget.

void ola::plugin::usbdmx::JaRuleWidget::RunFullDiscovery ( ola::rdm::RDMDiscoveryCallback callback)
virtual

Start a full discovery operation.

Parameters
callbackThe callback run when discovery completes. This may run immediately in some implementations.

Implements ola::rdm::DiscoverableRDMControllerInterface.

void ola::plugin::usbdmx::JaRuleWidget::RunIncrementalDiscovery ( ola::rdm::RDMDiscoveryCallback callback)
virtual

Start an incremental discovery operation.

Parameters
callbackThe callback run when discovery completes. This may run immediately in some implementations.

Implements ola::rdm::DiscoverableRDMControllerInterface.

bool ola::plugin::usbdmx::JaRuleWidget::SendDMX ( const DmxBuffer buffer)
virtual

Send DMX data from this widget.

Parameters
bufferThe DmxBuffer containing the data to send.
Returns
true if the data was sent, false otherwise.

Implements ola::plugin::usbdmx::Widget.

void ola::plugin::usbdmx::JaRuleWidget::SendRDMRequest ( ola::rdm::RDMRequest request,
ola::rdm::RDMCallback on_complete 
)
virtual

Send a RDM command.

Parameters
requestthe RDMRequest, ownership is transferred.
on_completeThe callback to run when the request completes.

Implementors much ensure that the callback is always run at some point. In other words, there must be no way that a request can be dropped in such a way that the callback is never run. Doing so will either block all subsequent requests, or leak memory depending on the implementation.

Also the implementor of this class may want to re-write the transaction #, and possibly the UID (changing src UIDs isn't addressed by the RDM spec).

The RDMRequest may be a DISCOVERY_COMMAND, if the implementation does not support DISCOVERY_COMMANDs then the callback should be run with ola::rdm::RDM_PLUGIN_DISCOVERY_NOT_SUPPORTED.

Implements ola::rdm::RDMControllerInterface.


The documentation for this class was generated from the following files: