Right now I've been maintaining a personal list of 39 bugs and suggestions... I'll respond to a few here:
1. They obviously have some sort of database of
IR codes. Sure would be nice to have direct access
to the database for viewing/matching.
Philips licenses its database from Universal Electronics, who is paranoid about theft. Thus, there is no way to see a complete list of what is inside.
2. I want to be able to control the first startup
page completely.
Although it would be nice, it's not overly critical as, once you're done, the remote rarely reboots. You can't really set it on the Pronto either.
5.On Buton Properties, the button position can
be edited, but while the size is shown, it cannot
be edited and is greyed out.
If there's a bitmap applied the button cannot be resized. If there are no bitmaps the size is editable.
7. Perhaps the ability to view memory usage and
possibly load the Pronto with multiple configurations
with the means to swap between them?
Due to the way PENG works with configurations, the file would need to be constantly compiled to accuratly see how big it was (that's what happens during the "preparing to emulate" stage). Once you start getting above 1 megabyte, the process gets incredibly slow -- it takes about 3 minutes to compile my converted ProntoPro CCF. Thus, you wouldn't want this going on all the time. :-)
8. I can't figure out how to read/export the built-in
IR codes. Of course I can see the learned ones.
As mentioned above, you can't. Even if you could see what "code" is used for a database function, it's only a pointer to the internal database on the physical remote. This is the way the original Pronto works.
10. Can I PLEASE label the learned codes? Having
the code in the edit window makes sense, but why
does this whole string have to show up in the
Label window?
Looks like a bug. Due to the way everything works right now, I think it's best to store actual codes on separate pages and link to them.
14. Perhaps a database choice where you choose
the REMOTE instead of the DEVICE. For instance
my Sony STR- DE575 reciever uses a Sony RM-U305
remote. This exact remote is used with numerous
Sony devices. Sure would make figuring out exactly
which code is associated with which button in
which mode.
So far no company has wanted to spend the time to try and create/maintain such a list. Hundreds if not thousands of new remote models are created by different A/V companies each year, even taking into consideration instances where the same remote is used by a few models (which is less common than you might think).
15. Obviously, Philips did a ton of research to
build the database in the first place. They obviously
also know DISCRETES are important to users of
Prontos. Maybe at the corporate engineering level
they could obtain COMPREHENSIVE lists of discrete
codes from all the included manufacturers.
As mentioned above, this is just UEI's big database exported for use on the Pronto. It contains some discretes, but it's a bit hit-or-miss.