Well I guess I have nothing to complain about now. :) Now I just have to site back and enjoy my remote instead of getting frustrated. I guess I can deal with that. Thanks a lot philips. Means a lot when you make a quick fix like this. Can't wait to see what new features will get added in future updates.

Ryan

Thanks for the quick update, ProntoTeam!

ProntoTeam, how about a firmware update that solves this problem on the ProntoPro NG? It has the same odd behavior.

Thanks!

I think the speed increase is awesome. I am very happy with the last two updates. Thanks ProntoTeam.

MThompson, I do agree that what I said is an overstatement. I know I certainly meant to have the word some in there. Quite a difference for one missing word.

Basically, I agree that the techincal features are all much better, however, many of the operational, hands on features are IMO a step down. This upgrade does go a long way toward making me love it like my 2000 instead of just liking it, but why a device that runs on batteries ever turns a backlight on when not specifically told to is beyond me.

The 3000 is an excellent remote in spite of these little shortcomings.

KML426 and Lee L:

Well thought -- well said.

I much more agree with you than disagree. I hope you know my dissents were shades of gray, not absolutes.

Thank you very much for the intelligent, reasonable, thought-provoking discussion.

I haven't had any time to mess with the 2 new updates, but everything i've tried works so far...

But here's my wish list....

1) Customizable Timer functions ..ie..
Let us have a Timer button wherever we want, in any device or panel we want, with any bitmap we want..as a special action and customizable setup pages.

2) The mentioned backlight on/not come on and 1-2 press preferences.

3) Lists..this is my biggie..
I'd love to be able to have the ability in PENG to generate sequential pages automatically..ie..setup a short template for index pages and list pages showing desired layouts and positions of buttons/lists, allowing me to make dvd,cd or channel lists easily while also allowing me to insert a new entry midlist without hassle, and without using another program. I've never used SNL, but sounds like it may be like that. Rambling here, but say i'd like to add an entry to the 3rd of 6 buttons on page 12, and have all following entries moved to the next position, and next page when necessary, and consequentially updating (don't know how hard this part is) the index pages.

oh yeah, i could see how someone would like an option to have two ir codes per button, one for use if pressed less than say .5 seconds, and one for when pressed longer than same .5 seconds. Me personally, would use two separate buttons for the different functions but maybe that's just me

like you, I don't like hat idea. I think, if anything, contact sensitive buttons would be much more interesting (i.e. simple conditional) could be useful for "advanced mode" when someone went through the password area (extra buttons), could be useful for people who have discrete codes when they wanted togle....

the idea of a touchscreen is to make it easier for every one to use. So if you need to spend time explaining short press....

My problem with the ne release is that drag and drop editing is basically useless. It used to be annoying, the editor would preferentially drop button properties (ie icon or actions) on the wrong button. It prefered to drop the properties on the frontmost button, not the one you were pointing at. With the new editor, it tends to drop the properties nowhere. At least 75% of the time I try to drag and drop the property I want moved ends up nowhere. This is very frustrating and makes the feature useless.

There is no reasonable way to move Icons and properties from one button to another.

What is so difficult about targeting the button I'm pointing at? There is no ambiguity in this. There is one point I am pointing at, there is one button in this place. How do you get this wrong???

What would be much more useful would be to have a selective paste function. You could copy a button, then select a button and choose selective paste. There could be someway to select what property (actions, Icon, label etc) you want transferred to the new button.

Currently the editor is frustrating and damn near useless in some circumstances.

(I've been working on such circumstances, I program a new IR command into the remote at home, I want to transfer this to the pcf file which on the computer at work. When it takes 20 tries to drag and drop the IR from the uploaded file to my master file, it get frustrating, when 25% of the actions get dropped on the wrong button it becomes useless.)

Does it take longer to learn IR in the editor? I wanted to learn an entire new remote (TiVo remote with a different ID). The first time I tried learning a button, I gave up before it learn. It took a surprisingly long time before it beeped.

I've never tried learning from this remote, but this seems exceptionally long. It took forevert to learn the whole remote.

I found the new calibration routine to be very frustrating. It would tend to pick up a double hit and fail the calibration.

Couldn't the calibration be a little more intelligent about filtering out double hits. If a second hit is less than half a screen from the first hit, and less than 0.? seconds from the first hit, its very likely to be an accidental double hit and should be discarded.

This got me as well until I experimented a bit and found out how it actualy works. The drop only drops onto a destination button directly underneath the top left hand corner of the button being dragged. This is not intuitive and it took me a while to figure it out.

Teresa

Thanks for the tip, it does seem to explain things.

That's braindead, not just not intuitive. I can be pointing at one button, while the top corner of the button is pointing at another, it ends up with the top corner.

This betrays a fundamental misunderstanding of user interfaces. It does not inspire confidence.

I've only used the drag and drop a few times, but it seems if snap to grid is enabled it is even harder to drop the buttons correctly unless your destination button is snapped to the same grid. For those having trouble you may want to disable that feature temporarily.