Can we change which keys are Grouped in rs2116/2117 ext2?

[MPSAN]

Boy, am I almost all set. If I can change a few basic things it will save me so much memory.

Here is what I want...

Since I don't look at the 15-2117 running ext2 in the dark, I use the pip button as TV MUTE. This is good as I can feel it as it is in the middle to the right of Volume. I also use FREEZE as FavChannels button as it, too, is in the middle to the left of CH. This is used to controll the CBL device (DCT6412). I use last and move to do a replay and 30 second skip...very nice.

However, it would be nice to just define VOL keys to use TV in phantom 1 and CH KEYS to use CBL.

The problem is that Vol Keys include the MUTE Button. Also, use freeze and fav for transport keys.

So, I was wondering if we could DEFINE which keys would be in "our own" SET_VOL_KEYS, etc. Even, for now, if we had to use a hex editor to move them around. It would so great if we could define our own "key sets".

So, any ideas, or should I load up on key moves?

P.S. I am using IR5.15 and Ext2.

Not sure IR 6.15 or EXT 3 would help anything.

[Capn Trips]

Well, since no real expert has jumped in on this, I'll tell you what I believe (and may be totally wrong). The keysets are actually a part of the remote's internal definition, and is not set by the RDF, nor by the extender. I don't believe it's possible (or at the very least likely to be costly in terms of effort to create and ultimately memory consumed) to re-define these keysets.

I may be wrong, but somebody smarter than me will have to tell you that.

[vasqued2]

You're right. The keysets are internally coded. There are some examples of old extenders show how you can include a table w/ new keysets but it would take up a lot of space and take away the space for keymoves and devices.

It takes a lot less space to use the internal table and override the keys you don't like with a keymove or two.

[MPSAN]

OK, all:

I was afraid of that!

Thank you,
Dave