Bob, I’m encountering the Javascript error messages that I mentioned about a week ago in a new context.
Old Context: set picking changeBond_# brings up an JS alert error box when you click an -H bond. The action is completed as in older versions of Jmol (14-2-4), but the alert box comes up. For better or worse, the end result is the same as older versions of Jmol - the hydrogens are deleted. This occurs on the Test2 page, so it’s not just my page. All of this is no big deal because this would only happen in an errant click. However... New Context: I’m now seeing this behavior in new Jmol (14.3.16) in another context where older Jmol (14-2-4) did not show the problem. Specifically, in experimenting with some asynchronous prompt boxes (JQuery and Bootstrap), I’m seeing this alert behavior if the prompt callback function contains JSmol JavaScript calls. This happens even if the JSmol call is unrelated to to the prompt box data. Again, the Jmol actions are completed, in this case correctly, but new Jmol puts up numerous JS alerts of the type in my previous note. Do the Old and New above hold async issues in common? JavaScript native prompt, alert, and confirm are, of course, synchronous. Otis -- Otis Rothenberger o...@chemagic.com http://chemagic.com ------------------------------------------------------------------------------ _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
