JP1 Remotes

Greg

I remember the discussion from way back when about why we used the format that we did for RDF names that support multiple remotes for RM but I can't remember why we decided to limit the name to the 4 characters like 9910 in each position..

This memory was triggered when I was trying to add the HTPro (5 chars) to the 8910/9910 RDF so I could add a separate image for the HTPro. I tried to add it as HTPro and of course what I get in the remote selection of RM is URC-HTPro, URC-8910o, and URC-9910o. Note the "o" on the names.

In order to make it work I had to limit the HTPro to HPro (4 chars) since all names are limited to 4 characters. I could actually use it's real designation of 9811 but everyone knows it as HTPro.

So, the real question is, is there a way to change RM to take anything between
1) the dash and the underscore,
2) between the underscores and
3) between the underscore and the ")"

as the name no matter what it's length is?

Also, is there a way stop the URC- from being part of the HTPro name?


OLD
CPT0CPT0 (URC-9910_8910).rdf

NEW
CPT0CPT0 (URC-9910_8910_HTPro).rdf

Nils,

The name isn't limited to 4 character, but RM does expect all names to be then same length. That's a silly restriction that I will fix.

RM searches for the underscores, then back tracks looking for a space, dash , or open paren. If there is a dash, it assumes that whatever comes before the dash is a prefix that is to be used with all names.

I suppose one thing I could do would be to only use the prefix when the partial name is the same length as the 1st partial name.

In your example, because HTPro is 5 characters which is different than the 4 characters in 9910, but the 8910 is the same length, we would end up with URC-9910, URC-8910, and HTPro.

The problem, of course, is that such a scheme is rather arbitrary and hard to remember.

gfb107 wrote:The name isn't limited to 4 character, but RM does expect all names to be then same length. That's a silly restriction that I will fix..

Now I understand why it worked the way it did.

gfb107 wrote:I suppose one thing I could do would be to only use the prefix when the partial name is the same length as the 1st partial name..

I think that would be fine and it would not require me to make many changes and would still help with the HTPro name.

gfb107 wrote:The problem, of course, is that such a scheme is rather arbitrary and hard to remember.

I didn't remember the current way so I will just have to try to remember a different way. And, it is mostly me it impacts.

Thanks

Greg, do you think you will be able to sneak this in or do you want me to enter a tracker for later inclusion?

I've already made the changes for this, but I've got some other stuff to finish up before I can release it.

Great, Thanks

I was just looking to finish another set of RDF's and was wondering which way to go with the HTPro