JP1 Remotes

Hi had an occasion to open this user's IR file for C7L0X7L5 extender.

https://www.hifi-remote.com/forums/dload ... le_id=7641

I didn't happen to have the RDF in the current folder, so it opened up the C7L0X7L0 RDF. On the top of the screen it said it was a URC-7800/6800 Extender on the raw data page it said C7L0X7L5.

Shouldn't IR complain that it couldn't find the proper RDF instead of opening another RDF?

Edit:

Apparently this has been the case for years. I have IR versions back to IR.6 on my machine, and its always worked this way.

But I still think that it is misleading.

I renamed the 7800 extender RDF files, leaving only the unextended C7 RDF in the list.
Then I loaded the file Vicky mentioned.
I don't know what RDF the IR app loaded, if any.
Indeed, no message from IR. The windows title included reference to ext5 based on the signature in the file.
The only difference from what Vicky saw (mangled key references) is that most areas were blank. No keymoves, only one power macro, no special protocols.

Oh good catch Liz. I thought the bug was just because the first 4 characters of the signature were the same, and that this was falling into the code for the remotes with 4 character signatures, but if you changed all of the extenders, then this could give you even weirder results. This could definately cause confusion for a newbie.

Is THIS the same issue? I think it was addressed by adding the new "Always Allow RDF Selection" option to IR8.

Not quite the same, but good point regardless. The 'Always Allow RDF selection' doesn't do it. It only works, i.e. issues a warning about missing RDF when there are no RDF files corresponding to the signature in the IR file at all, which, in my instance, means that ALL C7 files renamed and invisible to IR.

There's more to it than that. It also gives you a list to choose from when you have several RDFs with identical signatures like the radio shack 15-133, 134 and 135. So I would expect it to warn you or give a list when the RDF is missing or ambiguous. But I see isn't working like that with the file in question.