Hi,
I didn't owe a pronto so far. I just started to design a configuration with ProntoEdit to test if my desires would be satisfied with the pronto RC.

After discovering the product manuals and the different CCF's on remotecentral.com the design of "my remotcontrol" is quite clear. It should be an activiy based behaviour.

So the devices are activities. The buttons on the device panels are aliases to the learned IR buttons somwhere in the configuration. To store the learned IR Codes there are several places imaginable. Device section, Macro section and Home section.

What would be the best approach to store them?

Any help would be great.

Cheers, Danny

I would store individual IR codes on panels (perhaps hidden) in the device section. All other panels would then alias to these buttons. Macros, I would put in the macro side and alias to these.

In doing this, my goal is to be able to use the on-remote editing capabilities as much as possible. If you put the codes on the macro side, you would not be able to learn or re-learn without using ProntoEdit. If you put macros on the device side, you would not be able to edit the macros without using ProntoEdit.

Also, by having one copy of the original IR codes, you avoid wasting space, can change codes without affecting your other panels, and can edit your other panels without worrying about losing codes.

Good Luck,
Mike

I can't imagine why anyone would want to edit macros directly on the Pronto. So it does not really matter where they go.

I really have two types of macros - device speciifc that (often to emulate a discrete code), which I store with the learned codes for the device - and multi-device (such as set up everything for DVD), which I put on the button that I push to activate the macro.

As far as not keeping codes on the macros side, I actually do just that. I have one device per original remote control, and I keep all of these on the macros side. If I ever need to learn a code (and why would I once done?), I move the device back to the devices side, download it, learn the code, upload it then move it back to macros side. Sounds complicated but I only had to do it once.

Final result is
Home area: home page and menus
Devices area: device per activity
Macros area: device per original remote, plus stuff common to every screen (such as lights)