I've just started to create my own ccf. I've started by creating/copying some device ccf's (using default buttons) to use as "code pages". I plan to create "displayed" pages by creating alises to the buttons on the code page. Creating these alises through the menu though seems like a bit of a chore. Is there anyway to create an alias by "drag and drop", similar to copying button icons?

I've just started to play with prontopro. I've read the manual, the faq, and have lurked on the forum for about a week.

Thanks

This message was edited by work permit on 12/22/01 15:33.51.

Unfortunatly not.... (atleast that I know of) It is a chore, but allows you to easily update the .ccf for future equipment upgrades, so it's well worth the time and effort to do it that way!

Hmm. It seems to take me almost as long to alias a button as it does to learn it. In practice, this means a seperate code page isn't really buying me much.

Of course, on macro pages it makes sense

Am I missing something?

This message was edited by work permit on 12/22/01 17:51.35.

Yes, you definitelly want to create "code pages"! If you ever want to create a totally new CCF or just try out someone else's, you just have to merge the 'code page' INTO the new CCF and re-alias. This means that you do not have to re-LEARN all those buttons for a new CCF.

Click on Create an ALIAS.CCF, below.


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

This message was edited by MrKlaatu on 12/22/01 19:17.27.

One of the biggest problems is that newer versions of ProntoEdit don't remember where you were from the last alias. The software used to return to the last device/page when you pressed ALIAS a second time.

Hi Daniel

That makes a lot of sense...I've never tried the older ones. I've looked at your ccf, and noticed you didn't have a seperate set of codepages. Is that why?

By the way..fantastic ccf. I'll be sending you my paypal as soon as I get my pronto programmed (at this rate, probably by easter).

What tool did you use to create/modify your icons? I want to make some changes, I'm only familiar with photoshop.

No real reason why I didn't use a separate code page... I just didn't. :-)

Daniel, that is the most annoying new feature they came up with :-)

work permit: the code page has many advantages (in my opinion) there is the one mentioned by Mike, but there are a few more

2) if you change a piece of equipment, you can relearn all the codes much more simply (no need to find all the places it was used) plus you can add buttons you will not use on the UI

3) error protection

3 a) Some times when you are making a small change to the UI you might want to move a button to a different panel if you Cut and past that button every alias to it will be gone (happened to me)

3 b) the same thing can happen with copying panels

3 c) deleting keys by mistake

More on 2/ You can put every single code from your original remote into the code page even if you don't use it in your UI. This means that it does not matter if you lose the original remote or its batteries die. I lay out my code page to look like the original remote - this means that the original manual makes more sense when I try and figure out what the buttons are supposed to do.

4/ It takes a lot less memory as you only have one copy of each code.

5/ When posting your CCF to RemoteCentral it is much easier for other people to use your codes if they are laid out in a code page.

6/ If you find a UI that you really like, it is much easier for you to change your CCF to look like the one you like.

This message was edited by Peter Dewildt on 12/23/01 15:41.59.

There's no question in my mind that I should keep the all the codes in one place (ie macros, etc should reference the code in the device). I suppose I saw two choices:

1. Create a nice UI for each device, and learn the codes directly into the UI. Create a hidden page for any keys you don't want to have displayed in your UI. Reference the keys in the device page(s) when creating macros.

2. create a hidden code page(s) for each device. Learn the codes there. Alias those keys when creating a pretty UI.

I see the clear advantage of (2) if aliasing keys took less time than learning (or relearning) them. But at least with ProntoProEdit, aliasing takes almost as much time as learning (time to hunt down the key you want on the code page you want).

Anthony: Your points on (3) see quite valid (especially 3a). Boy, that would seem like a pain.

Peter, I do see your point in 5.

it happened to me when I first started out, so I know it was a pain.

Thanks again, Anthony. At least you saved me a lot of grief...

Well, I've begun setting up my code pages.

I notice that when I "merge" a codepage ccf into a ccf that has the same device name/panel on it, it doesn't overwrite the panel (it just creates another copy). So if I want to make changes or additions to my code pages AFTER I merged them with my main ccf, I have to make those changes in the main ccf.

I guess prontoedit wasn't designed with structured programming in mind. I wonder if crestron's VisionTools or Simpl Windows is as lame.

This message was edited by work permit on 12/24/01 11:07.20.

I think the names are labels to help with the design, and are not used by the Pronto. That is why it does not recognize TV.

I just thought of this, but if you install PE V1.05 on your PC and the icons are mostly the same (i.e. will not be much helpful for channel icons) you can use PE to make the CCF and then change the icons to the ones in color.