It would be *really* cool if the Lookup tool could create a .rmdu file. Seems like that should be pretty easy?
xnappo
Lookup Tool suggestion: create RMDU files
Moderator: Moderators
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
I don't know enough about RM or KM to build an upgrade. Someday, I plan to see how they are opened and parsed, but since I don't know java and by VB is weak, its not going to be done anytime soon.xnappo wrote:It would be *really* cool if the Lookup tool could create a .rmdu file. Seems like that should be pretty easy?
However its not all that difficult to create a sheet from the lookup tool using excel, so probably other spreadsheets with a cut/paste/sort ability.
I copy the information to excel, sort the data to get all the blanks out, because RM doesn't like it if you try to paste blank values, and then you paste the information into RM or KM's function sheet.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
The .rmdu file format is really simple. It should be trivial to output in that format instead of HTML. Here is an example:vickyg2003 wrote: I don't know enough about RM or KM to build an upgrade. Someday, I plan to see how they are opened and parsed, but since I don't know java and by VB is weak, its not going to be done anytime soon.
{RMDU file contents deleted}
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
If there is one thing that I've learned here, is that there is nothing trivial when working with the jp1 tools.The .rmdu file format is really simple. It should be trivial to output in that format instead of HTML. Here is an example:
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
While I am not planning on making an RDMU anytime soon, I've found the cause of my double spacing, and next month when I update my website, I'll remove the double spacing so that this will be more easily used for copy and paste solutions.
Edit, so much for next month. I edited the page, and now you can cut and paste without the extra line feeds. Its great with xl, and while its not the columns don't work in RM, at least you can get the complete list moved over for editing.
Edit, so much for next month. I edited the page, and now you can cut and paste without the extra line feeds. Its great with xl, and while its not the columns don't work in RM, at least you can get the complete list moved over for editing.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.