I would like to second Frieda's plea (Sept. 22, subject "Re: [Jmol-users] Prerelease 10.9.62") for restoring "set debugscript on" to usefulness for our purposes. Through 10.2, it was extremely useful to us. Since then, it generates far too much information, making it nearly impossible to find a simple error in a script.
Frieda and I are developing websites that generate complex, long scripts from javascript. It is very cumbersome to try to collect and run these scripts in the Jmol application. We need an easy way to see what we're doing in the applet. It was very helpful to see the actual commands listed plainly and readably in the 10.2 debugscript report, and the numbers of atoms selected, as well as the errors. We need to be able to see commands plainly and spot errors easily. We can no longer do either. Apparently "set logLevel" does not affect the output of debugscript. Perhaps we need some levels for debugscript like "set debugscript 1", "set debugscript 3", etc? Thanks, -Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
