Problematic file names

If you have a new remote that isn't recognized by RMIR, post the details here so we can help create a new RDF for it. Or, if there is an issue with an existing RDF or map, this is the place.
Post Reply
Barf
Expert
Posts: 1524
Joined: Fri Oct 24, 2008 1:54 pm
Location: Munich, Germany
Contact:
Contact Barf

Problematic file names

Post by Barf »

There are two RDF file which contain a space before the closing parenthesis. These are:

Code: Select all

remotes/rdfs/106A106A (URC-7780 Extender A2 ).rdf
remotes/rdfs/1A781A78 (URC-6820N_8820N_10820N Extender A ).rdf
This, apart from looking silly, causes a real problem in that a rmir file using that remote does not load directly: the remote is allegedly not found, and the user is prompted to select one. (I can give a more detailed description on request.)

Suggestion: rename those two files to

Code: Select all

remotes/rdfs/106A106A (URC-7780 Extender A2).rdf
remotes/rdfs/1A781A78 (URC-6820N_8820N_10820N Extender A).rdf
BTW, I consider putting information in filenames bad design :wink: .
Top
jgfarrell
Posts: 22
Joined: Mon Apr 12, 2010 5:40 pm
Location: Vancouver, Canada

Post by jgfarrell »

I'm still nursing along a fleet of extended 10820N's and have gotten the 'select a remote' prompt for a long time, without knowing why. I can confirm that removing the space in the filename as described does eliminate the prompt.
Top
Post Reply

Return to “JP1 - New Remotes & RDFs”