I've just about finished customising my CCF and have got as far as the Macros bit,
Is it really as simple as(for example):-

-Click on my (SYSTEM ON) button

-Click on Alias, locate the TV ON button from the tree and click ok.

-Click on Alias again, locate the AMP ON button from the tree and click ok.

-Repeat this for any other actions DVD/Sub etc?

I'm guessing i will need a delay in between each of these actions, but how do you know how much of a delay to assign(default being 0.1 sec)? Is it a case of trial and error?

Assuming what i've done IS ok, then what is the point of the Macro group(opposite the devices group) at the top of the Pronto screen, if i can peform a macro from a single button on any screen?? Thanks.....

Part, the first - Yep!, that's the way you do it.

Part, the second - Yep!, trial & error. But usually not between different devices, mainly between aliases to the same device, especially multiples of the same alias (ie; 3 > delay 0.01 > 3).

Part, the third - They are divided for those who do their programming on the Pronto as opposed to using Pronto Edit. On the Pronto, macros can only be put in the macro side . . .in ProntoEdit every button can be a macro.


MIKE

CLICK ON THESE LINKS
FAQ | Files | Reviews | Play with it | Phases | Planning | ALIAS.CCF | Copying .BMPs & Galleries | Discretes | Docking Station | NEO | X-10 | Parts | Cable | Buy/Sell

You are right, it is as simple as that and yes delays are trial and error (usually not needed when moving from one device to the next. Start with no delay and increase it if commands are missing. You want to keep the delay as short as possible, since longer macros have more chances of getting interrupted (someone walking in front putting remote down behind something....)

IN PE sections don't matter (Home, device and macro) and they are all equivalent. But on the Pronto they are not. On the Pronto each section does its own stuff.
Home: was a built to be autogenerating and work as a table of contents (TV, DVD....)
Device: was built for IR codes and each button has the ability to learn one command.
Macro: each button can access (alias) many other buttons, but they cannot learn any commands.

How are macros/devices used with PE.
1) if a button needs to be able to learn, it needs to be on the device side (not a big problem since you can later move it in PE and you don't tend to relearn often)
2) If (more important then 1) you want to be able to change commands in macros (timers) on the fly you need that button on the macro side (for example, during the Olympics I added a macro panel that had 4 rectangular buttons on it, I used Vol+ and - for the two Canadian channels covering the Olympics and one of the soft buttons for the US channel, the other four, I could change at any time to any channel I was more interested in)
3) (most used) when you flip from one device (macro group) to the next using the menu it opens the last panel you were at. When you flip between Macro, device and home, it opens up the last panel accessed in that section it can be used as a limited back function.

[Link: remotecentral.com]

Thanks, i just thought it sounded too easy!!

it is that easy :-)
And delays tend to be static for a device. So the delays needed for 123 will be the same as the ones needed for 234, but some equipment needs longer delays for a repeat key such as 112. And some functions (like a power on) force a longer delay, (but they don't tend to be used often and if it is repeated many times, you know the needed delay)