On 2005-06-06 (15:25) Miguel wrote: > >On 2005-06-06 (10:47) timothy driscoll wrote: >> >>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. > hi Miguel,
well, that does make me feel better. perhaps I stumbled across a more virulent error by accident. >Q: What is the behavior of the 'bad' script when using the Jmol >application? > apple.awt.EventQueueExceptionHandler caught Throwable : java.lang.NullPointerException java.lang.NullPointerException [...] no syntax error in the script window, though, which I have come to expect from Jmol script syntax issues. which supports the idea that this not a normal script error. >>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. > understood, of course. I was mostly blowing off some steam after a few frustrating days (I feel better now). I was also interested to know if this can be controlled from Jmol, or whether it requires a JVM change. >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. > ok, will do. > >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. > yes, this works great for scripts that I develop, and especially when I think I know what command is problematic. but, a friendly error-handling routine in the applet would help a lot when I have no control over the commands being passed. one example would be a command line interface to the applet; another would be a script file upload option for a user; a third would be a batch Chime-to-Jmol conversion routine. I will file a bug report for this particular command, and a feature request for the error-handling idea. thanks, tim -- Timothy Driscoll molvisions - see, grasp, learn. <http://www.molvisions.com/> usa:north carolina:raleigh "A debugged program is one for which you have not yet found the conditions that make it fail." - Jerry Ogdin ------------------------------------------------------- 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
