On 03/18/05 17:12 ET, Frank Weld said...
Ernie,
| I think I understand your design Ernie, So you
have on and off power buttons that alias the hidden
power panel? I had my original desin on my 2000
laid out like that.
There is no power panel at all. Instead, each component has a hidden panel (or more, for A/V receivers) with all of the commands on them, and I alias to these panels any time the codes are needed, whether it is the normal PLAY from the DVD transport page, or it is POWER ON as part of a home page macro.
Are yours on the Macro side as well?
My remotes have no macro side. I see no reason to have the client have to go to another place for any macro. HOME has all the macros. The component select macros (DVD, CD, etc) contain all the commands to turn the system on and switch things properly, and one grand OFF macro.
Other than that, what macros are needed? (nobody records anything, so stop thinking that)
I need to get some teaching on the Macro thing.
I had thought about having a window open after
touching the power plug on a panel that asked
if you wanted to turn the power on or off? Then
the reply would determine the next step in the
Macro
If your power commands are not all toggles, this can help. It is called "activity-based," and you can find some examples in the files section. I usually only have one or two components that do not have discrete power, and I just put a POWER button on the main page, then tell (with words spoken out loud) the user to turn the thing on if it is off. No Macro page, no Power page to go to...it's all right there.