RM Layout tab feature requests - phantom and reverse display

gfb107 · Post by **gfb107** » Thu Mar 10, 2005 2:45 pm

That's where I started, but I ran into some issues. In particular, what to do about functions that are assigned to buttons in a different shift-state than currently selected? I suppose I could just automatically change the shift-state so you can see the button. But what if a function is assigned to more than one button, and they have different shift-states? I also have to provide feedback about which function was selected.

Also, how to carry that function over to the Buttons panel.

Capn Trips · Post by **Capn Trips** » Thu Mar 10, 2005 3:34 pm

Having now looked at this with a few different remotes, extended and not, that I use, I find this an EXTREMELY useful development, for which I thank you mightily.

I remain (in the curiosity sense

) a bit puzzled by some of the behaviors/displays. I note that both versions (extended and not) of the RS 15-2117/2116 display seven phantom buttons, but the extended version displays 23

additional SET_XXX and DEV_XXX "buttons". On the other hand the normal and extended RS 15-1994 images display only the 6 phantoms in both. I expect this due to the way the device selection is set up in the 1994 extender, as it differs significantly from the 2116/17.

However, riddle me THIS, Batman, the unextended URC-8910 and HTPro images display three phantoms as buttons, as well as the seven "hidden" devices as buttons, while in the extended versions, the seven hidden devices are gone.

What gives with the inconsistency?

Or do I just really have to study how the various RDFs are constructed to see that the answer is obvious?

Nils_Ekberg · Post by **Nils_Ekberg** » Thu Mar 10, 2005 3:41 pm

Nothing gives with the inconsistency. I just have not uploaded all the RDF's that support Greg's latest changes. Some of the RDF's were previously updated for another reason regarding which buttons you can use and which ones you can't in RM and IR. Basically the change I have made to the RDF's is to hide the X_, T_ etc. buttons from RM.

When I upload the RDF's later you will see a lot more consistency.

gfb107 · Post by **gfb107** » Thu Mar 10, 2005 3:47 pm

The answer does indeed lie in the RDF files.

RM relies on the RDF to indicate whether a button is bindable or not. Bindable means that a function can be assigned to the button in a device upgrade. The default is for a button to be bindable.

So, the RDF for the extended RS-2117/2116 hasn't marked the DEV_??? and SET_??? buttons as non-bindable.

The 1994 RDFs correctly indicate that the X_???, V_???, T_??? and similar buttons are not bindable.

Similarly for the 8910/9910/HTPro the extender RDF marks the DEV_??? and SET_??? keys as not bindable, but the un-extended RDF does not.

The new visible phantom buttons makes these oversights much more obvious.

Nils is working on cleaning up all the RDFs.

Capn Trips · Post by **Capn Trips** » Fri Mar 11, 2005 2:32 am

Oh, OK.