IR.EXE feature request: Command line
Moderator: Moderators
IR.EXE feature request: Command line
1) Now that IR.EXE files have a fairly unique extension (.ir instead of .txt) it would be nice to be able to double click a .ir file and have IR.EXE start up and open it.
One can easily associate the extension .ir with the program IR.EXE (just double click a .ir file, and when Windows tells you it doesn't know how to open that it lets you browse to the right .exe). Then Windows will pass the .ir filename to IR.EXE as a command line argument.
IR.EXE seemns to ignore that command line argument and starts, but doesn't open the file.
2) There is an IR.EXE feature I've asked for, gotten, and lost again a few times as IR.EXE has evolved. When I've had it, it has been an important part of QAing DecodeIR.DLL, so that as I add new decode abilities I don't accidently break old ones. So far as I know this feature has been gone again for quite a while.
I want a way for IR.EXE to be started from a .bat file and open a specified input file (.txt or .ir), prepare a summary sheet including decodes of learned signals, write the summary sheet to an output file and then exit.
It should do that when it gets some command line more than just the .ir filename, such as getting two filenames as arguments (or a command line switch or however you prefer to do it. I care about the feature not the syntax).
One can easily associate the extension .ir with the program IR.EXE (just double click a .ir file, and when Windows tells you it doesn't know how to open that it lets you browse to the right .exe). Then Windows will pass the .ir filename to IR.EXE as a command line argument.
IR.EXE seemns to ignore that command line argument and starts, but doesn't open the file.
2) There is an IR.EXE feature I've asked for, gotten, and lost again a few times as IR.EXE has evolved. When I've had it, it has been an important part of QAing DecodeIR.DLL, so that as I add new decode abilities I don't accidently break old ones. So far as I know this feature has been gone again for quite a while.
I want a way for IR.EXE to be started from a .bat file and open a specified input file (.txt or .ir), prepare a summary sheet including decodes of learned signals, write the summary sheet to an output file and then exit.
It should do that when it gets some command line more than just the .ir filename, such as getting two filenames as arguments (or a command line switch or however you prefer to do it. I care about the feature not the syntax).
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Re: IR.EXE feature request: Command line
John, are you planning to use the sumary file just to look at or do you intend to use it as source data file to some process other than visual inspection?johnsfine wrote: I want a way for IR.EXE to be started from a .bat file and open a specified input file (.txt or .ir), prepare a summary sheet including decodes of learned signals, write the summary sheet to an output file and then exit.
If latter, I might piggyback a suggestion for a related, minor change.
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Right.ElizabethD wrote:John, may I assume we're refering the same File;Summary feature?
I'll be interested to see what you have in mind.ElizabethD wrote:I have an interest in format of data there, so I'll post a separate request. It should have no impact on your plans.
Hopefully someone who can preogram in Delphi will also look at these requests.
Try this version IR513Beta
The command line is like this
ir.exe inputfilename p destinationfilename
The p flag is to instruct IR to print the summary out the destination file. Without the p it will just open the file and display the summary page.
Notice that the inputfilename and destinationfilename should be fully qualified. However do not use any extension on the destination file name. I am using a .smy extension so as to not accidentally overwrite a .txt with the same name.
This is the first shot so we can tweak it any way you want.
The command line is like this
ir.exe inputfilename p destinationfilename
The p flag is to instruct IR to print the summary out the destination file. Without the p it will just open the file and display the summary page.
Notice that the inputfilename and destinationfilename should be fully qualified. However do not use any extension on the destination file name. I am using a .smy extension so as to not accidentally overwrite a .txt with the same name.
This is the first shot so we can tweak it any way you want.
Paul
That pretty much gets the job done.
When you just double click a .ir file to open it, I don't think it should open the summary sheet. It should be just like starting IR and then using file/open.
I'm not thrilled with IR.EXE appending .smy to the output filename. I'd prefer to have my .bat file in control of that. But it's not a big deal.
Thanks.
When you just double click a .ir file to open it, I don't think it should open the summary sheet. It should be just like starting IR and then using file/open.
I'm not thrilled with IR.EXE appending .smy to the output filename. I'd prefer to have my .bat file in control of that. But it's not a big deal.
Thanks.
-
Mark Pierson
- Expert
- Posts: 3017
- Joined: Sun Aug 03, 2003 12:13 am
- Location: Connecticut, USA
- Contact:
It still does the same thing. Are we clear on what issue we're discussing?e34m5 wrote:John, try it now.
There is no problem with the operation using the command syntax
ir.exe input_file p output_file
It opens the input, generates the summary to the output and exits, just as I wanted.
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 can't replicate this. On my PC it just opens the file....johnsfine wrote: 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.
What is the minor probelm you refer to.
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. Maybe you can create a text file and loaded into the diagnostics for me to see what you guys want.
Paul