![background image](http://html1.mh-extra.com/html/amx/rms-3-0/rms-3-0_manual_2938987093.webp)
i!-ConnectLinx
85
RMS NetLinx Programmer’s Guide
PULSE{VCR,2]
}
}
When the i!-ConnectLinx engine gets a request to play the VCR, i!-ConnectLinx
will "push" the button of the virtual device just like a user pushes a button on a
touch panel. There is now only one thing left to do: Tell the user which actions
are which.
In order to expose an action for execution via i!-ConnectLinx, you need to
support the programming for the action, as we have just seen, and you need to tell
i!-ConnectLinx what that action is.
To specify the name of an action, send a command to the i!-ConnectLinx virtual
device describing the name of a given channel code. To specify the names of the
actions in the above example, you would add some code like this:
DATA_EVENT[vdvCLActions]
{
ONLINE:
{
(* Setup actions *)
(* VCR Play *)
SEND_COMMAND vdvCLActions,"'ADD ACTION-1,VCR Play"
(* VCR Stop *)
SEND_COMMAND vdvCLActions,"'ADD ACTION-2,VCR Stop' "
}
Once i!-ConnectLinx receives these commands, it stores this information in an
XML file that can be used by i!-ConnectLinx compatible technologies to browse
available actions.
In addition to specifying the name of an action, you can also supply a help string
and a folder name. The help string helps a user understand the intent of the action
more clearly. The folder name allows you to organize the actions in a tree view so
that actions are more easily browsed.
Summary of Contents for RMS 3.0
Page 1: ...Software NetLinx Programmer s Guide RMS Resource Management Suite 3 0 ...
Page 4: ......
Page 10: ...Overview 2 RMS NetLinx Programmer s Guide ...
Page 12: ...System Requirements 4 RMS NetLinx Programmer s Guide ...
Page 22: ...Concepts 14 RMS NetLinx Programmer s Guide ...
Page 62: ...Custom Device Monitoring Programming 54 RMS NetLinx Programmer s Guide ...