They have been puting in stuff to make migration from V1.1 easier, and support for a new model Pronto. I was expecting it anyday now. But it is also summer holidays!

Lyndel, thank you for that information. That makes some sense and now I feel a bit better about moving to PEPV2 when it hits the street.

It seems that the new version will suffer from the same problem as the current version. If the exported command name does not exactly match the database command name, the IR codes cannot be bulk changed because the new and old models' command names will not exactly match. I find the current version to be worthless in this respect because database names are inconsistent, even within a particular manufacturer's models.

Lyndell,

So what you are saying is no more linking and use the database codes directly into the display buttons? I have done this recently and it seems to work fine and save many steps.

Please confirm my thinking is correct?

Thx Dave

Yes. You can no longer place IR codes directly onto buttons. You can only link to a code that is in My Database.

Dave,

Almost 7000 posts to choose from and you still cannot spell my name? :(

I agree. Maybe it's just the fear of change talking but out of everything I'm hearing about this V2, I don't like any of it. Is there anything really awesome about this new release that nobody has mentioned? Will this upgrade be mandatory? I'd like to stick with V1 if I'm going to hate V2 as much as I think I am.

I agree.

In the industry I work in, we usually ensure backwards compatibility. The idea that I would have to rewrite parts of my config (no more linking to hidden buttons) because the editor has changed is not appealing - and to be honest, slightly ridiculous.

The only implication I have seen is gui support of the rotary control based on comments from back when it was released. Hopefully, it's a lot more than this to justify the extra work especially since I just use javascript for the rotary. Whatever it is, the anticipation is killing me :)

Sorry, if this has been mentioned / asked before and I missed it, but....:
If I cannot directly link to buttons, will this also affect executeActions in Prontoscript?
I quite often use this to dynamically assign actions to one button.
Regards
André

Good point - I do the same.

I don't think there is any way it can prevent you having hidden pages with hidden buttons. So although you apparently can't link button A to hidden button B, I don't think this would stop you calling executeActions for button B (or C or D) from the prontoscript for button A.

Hey guys. It is backwards compatible. You just have to do a bit of work in V1.1 to move your codes to My Database before you upgrade an XCF. You can also run 1.1 and 2.0 side by side on the same PC.

Does NOT affect Widget.executeActions().

Which means I cannot simply load my XCF into V2 and expect it to work. That's not what I call backwards compatible.

Dave,

It is compatible in the sense that you will not lose functionality provided that you "migrate" to the new practice. I seem to recall, in early PEPV1 documentation, Philips "did" recommend that you place your codes into MyDatabase as a recommendation of "future proofing" your config.