> after several days, and much gnashing of teeth, I finally made The Grand > Discovery, almost by accident: > > > the problem was entirely due to an invalid script command. > > > I had an empty 'select atomno' in the middle of a long script. sure > enough: I deleted the offending command and presto! > > > now, I can't help feeling somewhat, well, misled. I guess I didn't expect > a command syntax error to be so deadly.
I agree. I also would not expect it to be so deadly. Q: What is the behavior of the 'bad' script when using the Jmol application? > so I'd like to make a request: > > would it be possible to implement a more user-friendly method for > capturing scripting syntax errors in the applet? I have a lot of irons in the fire and cannot undertake this at the present time. I cannot imagine why a script error would kill the JVM, but I cannot investigate it right now. Make a simple example for me, file a bug report with the example, and remind me of it occassionally. In general, I strongly recommend that script development be performed in the Jmol application. Save your scripts in files and use the 'script' command to execute them. Once they are running in the application you can move them to the applet. Miguel ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
