Command Line needs Error

Post your new features ideas and suggestions here.
Posts: 3
Joined: Thu Sep 10, 2009 3:59 pm
Location: Philadelphia, Pa

Command Line needs Error

Postby Agrarian » Thu Sep 10, 2009 4:06 pm

I want to use CompareIt! to generate comparison reports using the command line from scripts. One thing I have noticed, when using the /P and /G options, there is no way to see if there was an error.

For example, run from the command line: "wincmp3 text1.txt text2.txt /G:IS report.htm" when there are no text1.txt and text2.txt. The command prompt returns without showing the error that the files didn't exist.

There needs to be a way to either return errors to the command line, or perhaps better, write them to a log. I can see useful error trapping to include files not existing, permission denied to read file, path not existing for writing reports, no write permission for report location, etc.

Reed Technology

Site Admin
Posts: 1671
Joined: Tue Sep 23, 2003 7:37 pm

Postby grigsoft » Fri Sep 11, 2009 6:11 am

Idea with report is nice, I will add one. I will also add error return codes for batch use.

Return to “Compare It! - Suggestions”

Who is online

Users browsing this forum: Baidu [Spider] and 3 guests