The 1.5 version allows you to double click on the "LEARNED" code and proceed to give it your own label.
Trying this in version 2.0 results in no label, even though it apparently wants to let you label the code.
For now, I am just giving up until someone at Philips figures out a fix. And how does button ID Mapping work??? This is also an advanced item that is enabled when one correctly adds
(By editing C:\Windows\Pronto.Ini)
the extra line under the [version] heading:
developer = 1
This works in either version, but is a must in version 2.0 for hex code pasting and other advanced features to be present.
P.S.--Read my other thread on Font-Size enabling.

The workaround is to create a simple CCF in 1.05, create a panel with a button, paste your discrete code, give the button a name. Then open your V2 CCF and merge in the simple CCF.

Thanks Pete. Im starting to believe that it is easier to use Version 1.5 for all the programming, and then open the CCF I have created in version 2.0 to load it into the TSU2000. Why endure the extra work involved in the tedious extra properties widows. Frankly, I hate version 2.0!

But then you cannot use the UDB codes. Personally, this bug in PE v2.0 doesn't bother me. I do not care about labelling the IR codes themselves (I have mini buttons that I alias to on a hidden panel for each device, and these buttons themselves are labelled). And, I only use the emulator to look at my panel layouts, not actually test the codes - my computer is in a different room than my HT system! :o)

Tom C, V2 is certainly buggy, and what you suggest makes sense as long as you don't need to use the internal database.

However, when V2 is finally available for download (presumably as V2.1) these problems should hopefully all be fixed, and we'll move off V1.05.

If you look in the FAQ section on how to copy IR codes, you'll notice how many extra steps it takes in v2.0 over 1.05 to complete the same thing. Frankly, no change can be called an improvement if it involves more work. Trying to classify items under a myriod of progressively deeper windows isn't always better than just giving all options up front.