OK, I'm sorry to bother you pros out there, but when programming my Pronto Pro, should I load the IR commands into the current default graphics and then change the graphics, or should I load the graphics I want and then learn the IR codes into them. My guess is the latter, but I don't want to waste many hours and find out I screwed up!

Well, the best choice is neither one (IMHO). Use the software to create a device (call it IR codes). Put page(s) in this device with simple buttons on the pages, and learn or copy/paste the codes to these buttons. As you create your graphics/buttons for your other devices, alias to these codes. It has the advantage of only needing to learn each code once, and if you change gear it's much easier to reconfigure your remote. Do a forum search for "alias.ccf" to get more info.

Jim L

either way is OK. And I have flip-flopped many times on the best way to start. Learning to the default buttons gives you something usable until the real one is done, while the other way might eventual save some time. But what a lot of us do is use separate buttons for the interface and the IR codes. What we do is setup simple panels containing every function on the original remote (IR codes). Then we create the user interface on different panels and alias the UI buttons to the functional buttons. This way if you want to change the UI you don't risk killing codes or breaking aliases, also if you ever change equipment all the changes take place in one place (the hidden panel for that device)

Thanks, guys. What you said makes so much sense that I should have realized it in the first place - hence my "stupid question!"

I think it was a pretty good question! I have always first gone and looked for the graphics, but that is only because I immediately disliked the factory graphics, and there was no way I was going to teach commands to them.
It NEVER occurred to me to create simple hidden pages with all the commands on them, because I always do these for clients; I NEVER think of spending any time making the remote more easy to fiddle with. I think that is a really great idea, though, especially if the remote is yours. It allows you to pretty painlessly make major changes in the appearance of the Pronto.

So let me say, I am glad to see thoughtful answers t othat question.

Ernie,

Thanks for compliment. Not my original idea - but I've become a pretty good parrot.

If you program many of these in your business, it might make sense to adopt the approach. You could build a ccf broken down into types and models of gear (TV, DVD etc) and learn the codes to these pages. In other words building a library. When you have a job, just cut up the library to leave the gear you need and merge into your customers ccf. If you also have a library of stock ccf devices (again pages for TV, DVD contols etc) you could turn out a ccf in pretty short order.

Jim L

Ernie: like Jim said, it can also help with your installs, If you use different user interfaces, you can build a library of IR pages, let your customer pick the interface and then merge the IR pages with the UI and build all the links (aliases+ jumps)