Special Protocols section-command translation

Post by **ElizabethD** » Wed Dec 22, 2004 7:41 pm

To a LKP keys sequence keymove which was built in IR5 I added few commands using IR6RC3: DEV_TV;<commands>;DEV_CANCEL sequence on the Special protocols tab. The translation now reads
Key_104;<commands correctly translated>;Key_120. Is this how it’s supposed to be?

I built a new macro ,on a different key, with the same DEV_TV etc sequence, and here the translation is exact. It does not say Key_104…
Both versions work fine, so it’s not a problem for me, but I wondered if that’s the way it’s supposed to read. Should I adjust something, am I doing it incorrectly?

e34m5 · Post by **e34m5** » Thu Dec 23, 2004 4:35 pm

Looks like you may not have the correct RDF.

Post by **ElizabethD** » Thu Dec 23, 2004 9:44 pm

You maybe right but it seems inconsistent with what I see and I just checked the tail end again.
The fact that macro tab can display the entire range of names defined in the rdf but special protocol doesn't, makes me suspect the allowed range of hex values in the special protocols might be limited to $3F (phantom3). Assigned names for rdf values <=$3f are ok, while values $68-$7f gets those decimal translations tacked onto "key". I use 8910 extender in case that's relevant.
Limited range is a risky guess since I don't know what I'm talking about really, but all other stuff I wrote are facts.

mtakahar · Post by **mtakahar** » Fri Dec 24, 2004 2:21 pm

It doesn't seem to understand ":AllBind" in the RDF.