dvips fails to complete when you used in JPicEdt, but
it is possible to go to the command line and navigate
to the location of the dvi file and then it works
correctly.
I'm using this with Windows 2000. I don't have this
problem when using Windows XP.
dakota_curt@yahoo.com
Logged In: YES
user_id=412933
Hmm, sounds like a pretty difficult one to solve:
* what does dvips's output say (you may want to add a
"PAUSE" instruction in your script so that you've time to
read the output)?
* What scripts are you using? (eg, the default ones or
hand-tailored ones; in the latter case, please send them to
me).
* Have you already experienced similar problems with the
other programs that can be run from inside jPicEdt?
* Also: does the popup window that opens when you press the
"dvips" button freeze "open" (so that you've to press the
"KILL" button to close it) or does it close very rapidly
w/o dvips perhaps not having the time to complete?
I'm sincerely willing to help, but i need some more info!
Regards,
Syd, jpicedt dev team
Logged In: NO
I'm using the default scripts.
I've gotten all the other buttons to work fine. It's only
the dvips button that I can't seem to get working. I've
tried putting a pause in the script, but with or without
the pause the popup window "freezes" when it gets to the
command dvips jpicedt##### I've had to press the KILL
button to close the popup.
I have used a vi editor to look at the .ps file and the
file loads okay, but when I go to the end of it, it is
clear that the dvips command didn't complete. (The file
does "end" when I use dvips from the command line.)
Thanks
Logged In: NO
I neglected mentioning that I'm using content type
PSTRICKS. I forgot to mention this since the I've used
the same "pictures" on both XP and Win 2000 machines and
it worked with XP.
Logged In: YES
user_id=412933
Hi,
I've a user recently reporting to me that the same problem
occured to him, yet only in PsTricks content-type. LaTeX or
Eepic content-type worked fine. Would this be pstricks.pro
related? Or maybe this is encoding related, since jpicedt
and the shell do not necessarily share the same environment
variables (and this may --- or may not --- explain why you
get a freeze only when running dvips from jpicedt). What
does System.getProperty("file.encoding") say? (just open a
BSH console from the Script menu, and type in this expression).
As a workaround that may help debuggin, you may want to
perform the following steps:
1) create a simple drawing and press the TeX button in order
to generate a /tmp/jpicedtXXX.dvi temp file
2) then open a BSH console from the Scripts menu
3) determine jpicedt current working dir by typing "pwd();"
4) now copy the /tmp/jpicedtXXX.dvi file to this dir
5) then type in:
Runtime.getRuntime().exec("dvips jpicedtXXXX.dvi").waitFor();
in the BSH console, and see if a PS file get generated.
The exit code is <0> if everything went fine, <1> otherwise.
If a PS file got generated by dvips and you got an <0> exit
code, then there must be a problem in the way external
processes are handled by jpicedt on some combinations of
OSes and LaTeX distros...
Regards,
Syd
jpicedt dev team
Logged In: YES
user_id=412933
OK, after a couple of tests it sounds like the behavior is
different when using java 1.4.1 and java 1.5. I couldn't
reproduce the exact bug, but it seems there are some issues
in this respect when running jpicedt with java 1.5.
I'll think of switching to java 1.5's new process API when
we come to releasing jpicedt 1.5. Unfortunately for the time
being, jpicedt 1.4 must still be java 1.4.x compliant, and
it's out the question to switch to java 1.5 until all
platforms (including MacOS-X) have a perfectly functioning
JVM 1.5
Syd
jpicedt dev team
Pending on feedback from dakota_curt@yahoo.com