| Forum List • Thread List • Reply • Refresh • New Topic • Search • Previous • Next  1  |  1. ITERATEEXE#12654 | Having a problem with this and wondering how it should be called. I'm trying to call the Beyond Compare exe. In a DOS window, I can call it usingbcomp.exe @bc_batch.txt /silent The @ tells BC that bc_batch.txt contains a number of BC "commands". The /SILENT says I don't want to see any GUI window showing the results.
I've tried the following in RPC
compare_directory = 'c:\program files\Beyond compare 3'
compare_exe = 'Bcomp.exe'
bc_cmd = compare_directory"\"compare_exe
bc_batch_filename = "bc_batch.txt"
command(bc_cmd' @'bc_batch_filename' /silent')
The iterateexe is commented out 'cos I simply can't get it to accept the @ parms. The command line is not commented since this works fine.
Any suggestions on how to get this to work. (The documentation on ITERATEEXE is, to me, a bit confusing. I'm not really sure how the source, destination, before and after are suppose to be used i the example above). | 2. another thought #12655 | | It would be useful if ITERATEXE had a new option (D ?) for debug. I could see this splattering the actual command being sent to windows onto the console. That way it would be a LOT easier to see how the various arguments are handled/processed. | 3. #12656 | | I'm not surprised that ITERATEEXE doesn't work, whereas COMMAND does. The @ thing is a console redirection symbol. If Beyond Compare allows that, then obviously it's a console mode windows program that expects to be run from a console. In this case, you must use Command. That simulates being run from a console. ITERATEEXE offers no such console redirection. It simulates launching an exe by clicking on its icon on the desktop. | 4. #12659 | > The @ thing is a console redirection symbol
I didn't know that, I know that's not relavant to the issue, but useful info anyway, thanks Jeff :-)Doug | | Forum List • Thread List • Reply • Refresh • New Topic • Search • Previous • Next 1 |
|
|
搜索
论坛
Home
回顶部
g.yi.org Hits:0
