Installation guide

Macros - Resource Command
Commands
Commands are the actions executed when a macro is triggered. The list of commands is executed in order, and a
delay can be set before each command as a combination of seconds and milliseconds.
The list can be reordered by dragging the handles at the left of each row, or by clicking on the arrows on
the far right of each row.
Four types of commands:
- Generic commands
Generic commands apply to any area or zone, with the possibility of selecting the same area or zone
where the event was generated.
- Resource Commands
Resource Commands apply to a specific resource.
- System Commands
System Commands act directly on the systems, which support them.
- Macro commands
Macro commands call other macros, or act on other macros.
Command coding
Command coding commands are also represented by a code. The main difference is that there is a new
type of selector for matching the same area or zone as of the generating event.
A command code starting with $area/$zone/AV renderer/TV will act on all audio and video renderers named ‘TV’
on the same area where the event generated and a command code starting with */*/AV renderer/TV can be used
to work with all TVs in the house.
Actions on macros
A macro can contain delays between commands, and therefore take some time to complete. What happens if,
that during the macro execution, another related macro is called?
Several commands act on macros:
- FIRE: Call the macro, as if an event for that macro had happened. This is the default action.
- CANCEL: Will stop executing an on going macro.
- COLLAPSE:Will execute remaining commands in a on-going macro, but with no delays between
commands.
Firing another macro makes it possibly to take advantage of existing functionality without having to maintain
several copies inside different macros. It is possible to try a loop where a macro calls itself as the last command.
As a macro execution can take some time due to delays between commands, it is important to take care of what
could happen if another macro is triggered during the execution - for instance if a macro called ‘THEATER ON’
(for setting- up a home theater) takes more than one minute to execute.
What will happen if this macro is called repeatedly? Will all commands start to overlap each other?
What will happen if the THEATER OFF macro is called to switch the home theater off during the set-up?
It is important to understand that a possible messy overlap of command executions from different macros may
30