JP1 Remotes

When using Keymap Master 8.44(previous versions the same), when assigning functions to a button, the Comm Skip button is greyed out when 9910/8910/HTPro remote is selected.

I know this button isn't programmable unless you use an extender, but I am using an extender, so I'd like to assign a function to it.

Is there a way this button can be "ungreyed" in KM?

Thanx.

No.

You can assign keymoved functions to it in RM, which uses the rdf directly, (or directly in IR, of course) but in KM you can only assign functions to the keys allowed by the remote's native keymap.

(Just like many phantoms and all x-shifted buttons are available in RM, but not in KM)

This is one of those "damned if you do, damned if you don't" situations. KM used to let you program keymoves to the COMM SKIP button, but then we saw alot of posts similar to this one, except they were from non-extender users and they said "why doesn't my keymove work". So, it was disabled and now we get the same posts from the extender users.

Chuck_IV wrote:Is there a way this button can be "ungreyed" in KM?

As Rob said...

The Robman wrote:This is one of those "damned if you do, damned if you don't" situations.

There is a workaround however: use the Key Moves sheet to create the key move. For the function you want to assign to Comm/Skip select "(upgrade)" in the Bound Device column and enter "$2B" (the button code for Comm/Skip) in the Bound Key column. Then copy the resutling Key Move Code from the Setup sheet, goto IR's Key Moves tab, click the [Import] button, and paste the code into the Import Key Moves / Macros dialog box.

It's a little kludgy but can be used for any other extender-only buttons as well. It also allows you to keep all your button assignments together in the KM upgrade file for future reference.

Ah-ha! It's even in the readme.
Ok, so I tried this gem. It worked
But it looks like "(upgrade)" isn't treated the same as the upgrade device, which is Tuner here, so something is out of synch.
I expected
tune+ C6 C4 A7 E6 DF 9E
I got
Tune + (upgrade) C6 F4 A7 E6 DF 9E
When I changed (upgrade) to RCVR, then it was correct
Tune + RCVR C6 C4 A7 E6 DF 9E
What would be really useful at this point is to have an extra column on the Buttons sheet with the key numbers, or by whatever other means, to skip having to go to the RDF. Any chance?

ElizabethD wrote:But it looks like "(upgrade)" isn't treated the same as the upgrade device, which is Tuner here, so something is out of synch.
I expected
tune+ C6 C4 A7 E6 DF 9E
I got
Tune + (upgrade) C6 F4 A7 E6 DF 9E

The F4 is correct for "(upgrade)". It's interpreted and changed by IR to be the device assigned to the upgrade. It's the same for key moves created on the Buttons sheet.

What would be really useful at this point is to have an extra column on the Buttons sheet with the key numbers, or by whatever other means, to skip having to go to the RDF. Any chance?

If KM had access to those key codes it could support them all. However, it doesn't and therefore can only support the "standard" buttons.

When you select (upgrade) as the "Device" to which you're binding a keymove, KM does not know (nor does it have any way of knowing) to what device you intend to assign that upgrade - hence to which device to bind that keymove, so I would wager that F4 is a "holding" hex code that becomes the correct code once you paste the upgrade into IR and select the device to which the keymove will be bound.

When you select the RCVR device as your bound device, then you get the RCVR device hex selected immediately in KM.

What d'ya mean KM does't know what is the upgrade device? It says TUNER on the Setup sheet. I've done keymoves before for upgrade and others in KM (though moved into doing it in IR for system-wide things), still, this is puzzling
Now, since both of you basically said the same thing, I believe the "holding" concept ... ok, I'll check it out some more. Good to hear is not an issue.

Regarding button numbers. Oh, well. Hey, Mark, would it be a real big redesign to use RDF the way ECC uses it? It's such a cool thing to be able to have the complete upgrade all in one place, it might be worth it

ElizabethD wrote:What d'ya mean KM does't know what is the upgrade device? It says TUNER on the Setup sheet.

In this case, TUNER is the device mode, but that doesn't tell us which device button you intend to use. After all, you might want to program this TUNER upgrade to the CABLE device button.

ElizabethD wrote:What d'ya mean KM does't know what is the upgrade device? It says TUNER on the Setup sheet. I've done keymoves before for upgrade and others in KM (though moved into doing it in IR for system-wide things), still, this is puzzling

Uhh.. ????
In KM you assign the DEVICE TYPE, but you do NOT assign it to any particular DEVICE BUTTON until you're in IR, where you have to make this assignment on the General Tab.

What part of this is a new concept, Liz? You've been around a while.

oops
You know how to use it and screw up the meaning. But you know what? it says Bound device as the column heading. Anyway thanks for making me think straight.

ElizabethD wrote:it says Bound device as the column heading

That it does. Remember, Bound Device and Device Type are not the same (as Rob already pointed out). If you look closely at the drop-down in the Bound Device column you'll see that it contains the named device buttons and not the list of available Device Types (like on the Setup sheet).

Mark Pierson wrote: It's the same for key moves created on the Buttons sheet.

I completely forgot about this "F" convention for all upgrade keymoves. Long ago Greg explained it quite thoroughly for pause or something and after your answers it got reconnected here. Sorry for causing dumb trouble

Mark Pierson wrote: If KM had access to those key codes it could support them all. However, it doesn't and therefore can only support the "standard" buttons.

Mark, I did not mean all keycodes, just a new columnA with hex base numbers next to the button names on the Buttons sheet. The user can OR as needed for the Keymoves sheet. The point is to have all needed building blocks in one place (KM) and not have to hunt through RDF.