Parker PHD28, Руководство пользователя, Страница: 84 / 157

6
DCP Management Events
2 Application Programming Interface (API)
PHD API Reference
DCP Management Events
phd.subscribe
Event
phd.subscribe
Event Data
Keys Values Description
event
<event_name> Space-separated list of the events to subscribe to.
receiver
<IO channel> Storyboard IO channel to receive these events.
Direction
output
Channel
any
Notes
Sent by the application to tell DCP it wishes to subscribe to a particular event or
class of events.
For example, to subscribe to the system hardware interface backlight events, send
the
phd.subscribe
event to the system hardware interface channel ("nxs") with data
containing the event name and the IO channel name of the receiver (usually the
Storyboard application name).
("event", "<event_name>")
("receiver", "storyboard_app.gapp")
If the application does not subscribe to a class of events, it does not receive them.
This avoids the problem of DCP flooding the application with every DCP message
in the system. Subsystems can communicate with each other via DCP without
disturbing the application.
Please note that Lua examples for received events assume that the Storyboard
application has subscribed to the event via this mechanism and reception of the
event is set to trigger a Lua function.
Also note you do not need to subscribe to a channel to send events to it.
Lua Example function register ( mapargs )
local data = {}
data [" event "] = " nxs.backlight "
data [" receiver "] = " storyboard_app_name.gapp "
gre. send_event_data(" phd.subscribe ",
" 1s0 event 1s0 receiver ",
data , " nxs ")
end