Defining Device Macros
95
VisualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
Defining Device Macros
Overview
Use the options in the CodeBuilder dialog to define macros for buttons associated with third-party
(controlled) devices in your system.
Button Event Handlers
There are three types of Button Event handlers supported by VA CodeBuilder, and you can assign
macros to all three:
Push
- Specifies the actions that should be performed when a button is pressed. By default,
Push events are used by all events.
Release
- Specifies the actions that should be performed when a button is released (after a
Push).
Hold
- Specifies the actions that should be performed when a button is pressed and held for a
minimum length of time.
The Hold Duration (the minimum time required for a Hold button event) is specified in
the Button Event Options dialog (in 1/10 second increments).
By default, the minimum time required for a Hold button event is 5 seconds (Hold
Duration = 50).
Codebuilder Dialog
Select
CodeBuilder
from either the Device Menu, or the System Diagram context menu to access the
CodeBuilder dialog, where you can design macros for controlled devices and keypads in your system.
This dialog contains its own Menu Bar and Toolbar.
This dialog is divided in to three main sections (left-to-right):
User Interface Buttons Window
The User Interface Buttons window displays the UI buttons available for the selected device. You can
design a macro for any or all of these buttons (FIG. 71).
A
macro
is a series of commands and procedures that are carried out in response to
a single button event. Macros are typically used in control systems to allow the end-
user to trigger several events from a single touch panel button.
For example, a macro could trigger a lighting scene, cause a projection screen to be
lowered, power up a DVD changer and other associated A/V equipment and set a
particular volume level, all from a single button event.
This option is only enabled if you have selected a third-party device in either the System
Diagram or the System Tree.