Sorry Phil, I wasn’t clear. I mean both pages were driven by the same JSmol/JSME code. In other words, the problem is something on that Jmol/JME page template. I see the convenience of .js code that merges Jmol and JME, but I’ve always used these as separate entities on a page. With advances in Jmol over the years, communication between isolated Jmol and JME is really pretty simple. I take the isolation as far as putting JME in an iFrame.
One nice thing about JSmol and JSME is that they aren’t going to work on old browsers! You don’t have to write for older browsers other than indicating that users need to update. I bring this up in the context of iFrames. I don’t think they are the no-no that they were in the past. Otis > On Jun 18, 2015, at 9:36 AM, Philip Bays <pb...@saintmarys.edu> wrote: > > In the same folder as what? > > J. Philip Bays > Emeritus Professor of Chemistry > Saint Mary's College > Norte Dame, IN > > Sent from my iPad > > On Jun 18, 2015, at 1:05 AM, Otis Rothenberger <osrot...@chemagic.com > <mailto:osrot...@chemagic.com>> wrote: > >> Phil, >> >> I'm at a loss other than saying that there is something inherent in Bob's >> JSmol/JSME page that is causing the problem. If you use >> >> jsmol/jsme/JSME.html >> >> in the same jsmol folder, then the problem goes away. Clicking anywhere in >> the FG icon drops the menu. >> >> Wild, I don’t have a clue, guess: Bob does redefine the JSME jsmeOnLoad >> function in his page. Peter’s page has a code comment that suggests that >> loading with this on load function is important with respect to proper >> applet element display. Maybe the new jsmeOnLoad function is causing the >> problem. >> >> Otis >> >> >>
------------------------------------------------------------------------------
_______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
