IR.EXE feature request: Command line

[Mark Pierson]

I was able to import to Excel the output from the summary page with no problems...so I am still at a loss to understand.

Was that using the file saved from the Export to File button or copied and pasted from the summary display? When I use Export, I get a single block of unformatted terxt... no tabs, no line feeds, no delimiters at all. Excel cannot digest that in any shape or form. Copy from the summary display works because it contains the delimiters.

Text to be imported into Excel needs to be one of the following formats:

1) Delimited fileds (using <tab> or ",") with each line terminated with a line feed.

2) Fixed-width fields with each line terminated with a line feed.

Anything else just confuse the text importer.

Basically, the biggest problem with the current full summary display is the multiple tab characters in the Key Moves section between the "Hex Cmd" and "EFC or Key Name" fields; if you remove them and use a single tab, everything will be fine. Then, you can just export that text to a file as is using the Export button.

[e34m5]

Ok

[Mark Pierson]

There is a minor isuue using the command
ir.exe input_file

That is the command Windows uses if you associate the .ir extension with ir.exe and then double click a .ir file.
That ought to just open the input. Instead it opens the input and opens the summary sheet.

I'm having the same problem as John. I have NOT setup a file association for the .IR extension; instead I'm using drag and drop from within Explorer. The file opens and immediately displays the Summary window.

You need to check whatever code you added for parsing the command line. If there's only one parameter, the Summary function should NOT be called.

[e34m5]

I fixed the minor issue.....dumb programer error. Double click and drag and drop should work fine.

The file that is exported from the summary should work fine in Excel now.
However, when I fixed the formatting for the export I messed up the one in the summary. I'm really trying to avoid writing to sets of code for this.

Sp give it a try it's Betav4.

[Mark Pierson]

Double click and drag and drop should work fine.

I can confirm drag & drop works fine.

The file that is exported from the summary should work fine in Excel now.

It does.

However, when I fixed the formatting for the export I messed up the one in the summary.

How so... because the columns don't align when you have long Hex Cmd's? That's the way it used to be. Most people will be using the output in other apps where the tab settings can be controlled, or control the delimiting of fields. Just because it doesn't look pretty on the summary display isn't necessarily a bad thing... you can't use that for much of anything anyway.

[Mark Pierson]

The file that is exported from the summary...

One more minor complaint.

When naming the file to be saved, one must explicitly add the extension (if saved as "ThisIsMySummary", that becomes the filename without an extension). I think you should default to the standard .txt extension since they are plain text files (I assume the File Save control tests for the existence of the file before saving to prevent overwriting?).

[e34m5]

Well if the display is not an issue I won't worry then. I was trying to make it pretty.

I'll default the extension to .txt. If there is anything else let me know, otherwise I'll put this one out tomorrow.

[The Robman]

Thanks for your efforts with this Paul, it sounds like you've taken IR yet another step forward.

[e34m5]

TX

[e34m5]

I found the offensive code in the Copy function. It was actually a constatn that I did not see before.

Everyone try it now and let me know it we are good to go.

[Mark Pierson]

I found the offensive code in the Copy function.

I think you finally got it! The [Copy] button on the Key Moves tab now has the same header as the full summary.

[ElizabethD]

Everyone try it now and let me know it we are good to go.

Paul and Mark,
New IR export and clibboard jobs are a joy to use. Slick and clean. Thank you VERY much!