routing the IR to a specific IR-port (if an AX-R4 is used). See
Devices
for
more information.
o
RS-232 commands will be transmitted once. Unlike IR-commands, RS-232
commands must be used in combination with a device (see
Devices
).
o
If the object is a page, it will be loaded and displayed. Pages can be dragged
from the resource list into buttons or their action fields.
o
If the object is a macro, it will be executed. Macros can be dragged from the
resource list into buttons or their action fields.
Long press duration
is visible when a long press action is defined. This is for
setting the delay before a button press is deemed to be a long press. If the button is
released before the time expires, the short press action is executed.
Button Image Components
Buttons are composed of up to five image components:
The “Unpressed” image is the default image that is normally displayed. This image
type is mandatory.
The “Unpressed – active” image is displayed when the user is not pressing the button
but the button state is set to “active”. This occurs for some button classes when
feedback from the network has been received that the selected function is enabled.
For example if the class is “Mute”, the button will be active if the selected zone is
muted. This image is optional. If not defined, the “Pressed” image will be displayed,
if available.
The “Pressed” image is displayed when the user is pressing the button. This image is
optional although its use is recommended for providing visual feedback and
enhancing the user’s experience. If not defined, the “Unpressed” image is displayed.
The “Overlay” image is drawn over the top of the main button image. Similar looking
buttons with only minor differences are composed using overlays. This makes it
unnecessary to create many different button images and unnecessarily waste
memory. For example an array of buttons for source selection could be created,
which all use the same basic button images but with small text overlays such as
“CD”, “DVD, “Radio”, etc. The use of this image type is optional. If not defined, no
overlay is displayed or an overlay may be derived from the button command, if
supported.
The “Overlay – active” image is like the “Overlay” image but is displayed when the
button is active. This makes it possible to change a text based on the button’s state
(e.g. “mute” vs. “muted” or “unmute”) or to display different images such as the
image of an LED that is illuminated or not. The use of this image is optional. If not
defined, the “Overlay” image is used, if available.
If the button’s primary action is an alternating macro, overlay images can instead be defined
for each command in the macro. Alternating macros toggle between two or more commands
and by using button overlays in the macro, the button can reflect the next command in the
macro’s sequence. The button’s own overlay images have priority so these must be left
undefined if overlay images from a macro are to be used.
Images are standalone objects and are only referenced by buttons. As a result memory usage
increases only when a button is first added to a configuration. Adding buttons that use the
same images will not increase memory usage further. Customizing the buttons by using
18
