With my RCA remote, I am trying to do everything using RM/RMIR. One nice feature is that once you import a device, you can edit directly in RMIR. A minor issue I noticed is that changes you make are NOT saved in the original .RMDU file, but only in the .RMIR. I know there is a 'save as' option, but you have to remember to do that every time if you want a backup.
A nice feature, if it doesn't already exist, is for RMIR to remember a 'link' to the original .RMDU file, and offer to update it (or them) whenever the RMIR is saved. This could be an option that would be turned on or off, depending on how people feel about it. I wouldn't think it would be too hard to implement.
Auto-update .RMDU files from RMIR
Moderator: Moderators
I also see this as a problem. From the normal software-engineering process, it is nasty when a tool "snarfs" the content of (possibly versioned) source file (i.e. the upgrade; *.rmdu), makes its own copy and makes changes to that copy, which is then versioned separately. (Yes, I keep my rmdu and rmir-files in the subversion version management.) The suggested solution does not really solve the problem.
I am not sure of a proper solution. (RM)IR keeps only a very "compressed" version of the update in the flash image. RMIR additionally includes the "source" of the upgrade as [DeviceUpgrade] as text in the rmir-file. Possibly it would have been better to use a file name, in which this information is store (= the original upgrade file). Of course, it has the disadvantage that several files have to be maintained.
I am not sure of a proper solution. (RM)IR keeps only a very "compressed" version of the update in the flash image. RMIR additionally includes the "source" of the upgrade as [DeviceUpgrade] as text in the rmir-file. Possibly it would have been better to use a file name, in which this information is store (= the original upgrade file). Of course, it has the disadvantage that several files have to be maintained.