Quote:
Originally Posted by enarchay
I was trying to use the GUI, but it won't work because the command line program only opens for a split second and then closes. So, for example, if I hit "process," the command line opens for a split second, but it doesn't process the file since it closes too quickly.
I don't know much about using a command line program. I tried to use it through the CMD window and it wouldn't convert either of the two PDFs I tried - maybe I did something wrong.
|
Your problems are probably related.
All the GUI does is take the options you give it, and call the commandline program. It doesn't even check the output of the commandline.
I wrote for the GUI, "It's very barebones, and not at all idiot-proofed. (E.g., it does not check to make sure the options make sense, it will not tell you if SoPDF encountered errors, etc.)"
If SoPDF encounters errors when called from the GUI, the command line will open, show the error message, but then close immediately. Not very helpful, I admit, but my goals were very limited when I created the GUI. I was mainly doing it for my own convenience, but I thought I'd share just in case anyone else found it useful.
However, if you run sopdf directly from the commandline, the error message should stay visible. What does it say? What options are you using in particular?
Maybe that'll help us figure out what went wrong, though there are some pdfs. I've just never been able to get it to work right with. I don't know why. I had hoped to look at sopdf's source code at some point, though I've been far too busy.