JP1 Remotes

asinsh · Joined: 05 Aug 2003 Posts: 66

When I installed extender2 for the 2116 last night and it carried over my keymoves, device selections, upgrades, macros, etc. I was quite pleased. I was even more pleased when I saw that it had gratuitously set up for me simple macros on unused device keys and the phantom 1 key that in effect fully defined those device keys (e.g. CBL was given a macro that reads DEV_CBL; phantom 1 and then phantom 1 was given a macro that set all of the types of buttons to the active device; similarly SAT was given a macro that reads DEV_SAT; phantom 1; etc.).

But the one thing extinstall didn't do was to convert each of the device key calls I had in my already existing macros into the corresponding 'DEV_' key. For example, if an existing macro says TV; power; Audio; power, etc., I would think it would be useful for extinstall to change that to DEV_TV; Power; DEV_AUD; power, etc. This would probably help people with lots of macros who are converting over to the extender for the first time.

Am I corrrect that it would be as simple as having extinstall change every occurrence of a device key to the corresponding DEV_ command in every macro, or is it more complex than that?
_________________
Alan

johnsfine · Posted: Fri Jan 16, 2004 10:14 am Post subject:

I think it's a little more complex than that. How do you know it isn't correct to invoke the nested macro to fully select the device? Not all extenders use that DEV_ convention. Should extinstall make such assumptions about button naming rules?

Actually extinstall is doing much less than you gave it credit for above. It is just merging the macros and keymoves from your configuration with the macros and keymoves from the extender's hex file. The phantom 1 and other things you mentioned were put in the extender hex file by the author of that extender.

Anyway, the source of extinstall is available and pretty simple C++ code if someone wants to add some features.

asinsh · Joined: 05 Aug 2003 Posts: 66

You're right, John. I had incorrectly assumed that the extinstall program was just for this particular extender and this particular remote. If that assumption had been right, I think my suggestion would have been workable since I think that the unextended 2116 does not permit nested macros so any reference to a device key in a macro written for the unextended remote would (I think) necessariily have been an attempt by the macro writer to put the remote into the mode of that called device.

Anyway, this only comes up the very first time someone switches to an extender so it's no big deal one way or another.
_________________
Alan

johnsfine · Posted: Fri Jan 16, 2004 1:45 pm Post subject:

vasqued2 · Expert Joined: 03 Aug 2003 Posts: 67

And it gets even more complicated if you try to convert from one extender version to another if they use different device selection mechanisms.

For instance, v1 of the 2116 extender uses the X_ device selection mechanism and v2 used the DEV_ selection mechanism. I think at least some of the 1994 extenders would have the same issue.

In the end, probably a lot of complexity for very little use.

David