We all know that building a configuration file can be a daunting task. (I've been working on mine for a month and a half.) Making things more difficult is the fact that we all have to deal with non-discrete toggle codes. It would truly solve a ton of problems if every device had discrete codes for every action. It seems to me that it would be very simple for remote manufacturers to design a remote that could "remember" which "state" the device is in negating a need for a discrete code. For example, say your configuration has 6 devices. Let's assume that three of those devices are already on. You've built a macro that shuts the entire system off but the remote "remembers" which devices are already off so that it won't turn them on during the macro. Does this make sense? I mean, how much processing memory would be required to do this? 2kb, maybe? Do the mega dollar Crestrons and Niles have this feature? It just seems so simple to do and would solve so many problems. What do you think?

Wouldn't be tooo hard to implement, but extremely usefull.

Look at the MX950 review:
[Link: remotecentral.com]
A (simple) solution like this would be enough for most of our needs.

The problems resulting of not-receiving one or more IR-Commands would last, but that's nothing variables are guilty for. ;-)

Greetz
Jochen

Yes, this is exactly what I'm talking about. Variables! I could live with the non-receiving issue. It's a small compromise if you ask me. No firmware update required. It could be added to the programming software. (PPENG). Why won't Philips do this? Oh, the headaches that would go away!