On 2016-02-08 15:51, Robert Hanson wrote: > Pretty sure this is just the need to use > > var errors = Jmol.ScriptWait(myJmol, jmol_script);
Thanks Robert. After correcting the typo to Jmol.scriptWait that seems to work. I wasn't using it because of what it says at: http://wiki.jmol.org/index.php/Jmol_JavaScript_Object/Functions#scriptWait "NOTE: When using JSmol/Java do not call this method from a callback directly, as it may result in Java thread lock, causing the entire browser to hang. Always consider using evaluateVar() instead of scriptWait." Since I am calling it in a callback, should I be worried? And can I safely ignore the return value, which appears to be a sequence of apparently random status messages? Thanks, Dave > not > > var errors = Jmol.evaluateVar(myJmol, jmol_script); ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
