Just got my Pronto today and wanted to start laying everything out in ProntoEdit. I thought the easiest way for me to do this for my 8 remotes would be to make a hidden panel(s) for each remote with tiny default buttons, and use these panels to store all the codes. Then I'd create the real panels and reference the aliases on the hidden panels. Is this efficient memory-wise? It seems to me that this would allow me to play around with the UI pretty easily.

I believe this is the best way to use the Pronto - Storing the IR codes on simple buttons with no graphics and then using an alias to the buttons when ever you want to use them. You can change a great deal of the UI without screwwing up your IR codes.

Joe P, I second West's opinion. This method is memory efficient, straight-forward, relatively simple, and it works great!

Thanks for the replies. I'm a software developer by trade, and always seperate the UI from functionality. This seems no different to me. I just wanted to make sure this wouldn't chew up alot of memory.

Unless you're going to be concerned about a percent or two of memory, that's the best method when you really aren't sure what sort of design you'd like.

Which one of you out ther has a good ccf where you hid the original remotes with all your codes? I would love to see how this is done (how the buttons are labeled, the size and shape, where the remotes are on the prontoedit "tree," etc.). I have had my Pronto for a while, but I have yet to dive into it (mostly, I haven't had a spare hour in the last few months). Anyway, I am going to start soon, so any info would be helpful! Thanks,

Chas

Chas, it's not what I'd call a finished, or polished product, but I'll e-mail mine to you so you can how it's done.

Chas,
I've emailed you my current CCF which uses hidden panels for all IR codes. Each device has an IR code hidden panel that contains all of the learned codes for that device. Each GUI button just has an alias to one of the buttons on the codes panels.

Floyd

Chas,

Here's another one. I've placed alle the IR codes in a macro group, so they are never in the way when you edit your device panels.

Guido

Thanks everyone for all your help. I think I have more than enough to get on my way!

Chas

One suggestion I have is to label the buttons quite discriptively. I hade all kinds of trouble using the the symbols for ff, rw, play, stop, ect. I changed to a smaller font that does not support the system fonts and had a heck of a time figuruing out which strange symbol went with which IR code. I eventually gave up and renamed them all.

Good Luck!

Will

Hello, I'm a retired person who is not very experienced with programming. Would someone please also email me an example ccf file with the hidden buttons - the idea that separates the GUI from the functionality makes a lot of sense, and I've read that by doing this you can make changes and not have to re-learn all over again.

I've been a little afraid to get into this, but maybe this will get me started. I guess since I have the original ccf saved I can always get out of trouble!

Thanks very much!
Dave