Pat,
If you are using Jmol buttons in the control frame, you might want to try the
following for the Jmol object definition in the Jmol button function:
parent.document.getElementById("modelFrameID").contentWindow.yourJmolObjName
I THINK this is a correct JavaScript frame to frame reference, but I do not
know if it will work inside the Jmol button function. When frames are not
involved, yourJmolObjName would be the direct reference to your object. Again,
I THINK the above is the correct JavaScript frame to frame reference.
Otis
PS
On another note, did you know that CCDC has their complete student data set
available for download?
--
Otis Rothenberger
o...@chemagic.com
http://chemagic.com
> On Apr 2, 2015, at 9:51 AM, Pat Carroll <carro...@sas.upenn.edu> wrote:
>
> I have many old html web pages with previous versions of Jmol (as far back as
> version 10!). Now that I’m converting to JSmol, I find that those pages that
> use html-coded frames don’t work. I have the JSmol display in one frame and a
> menu script in another. The display works and any script commands in the same
> frame as the JSmol display work, but the menu scripts in the other frame do
> not.
>
> Is there a reason for this? Is there a way around it?
>
>
> Pat
>
> Patrick J. Carroll, Ph.D.
> Director, X-ray Crystallography Facility
> Department of Chemistry
> University of Pennsylvania
> Philadelphia, PA
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
