Bob wrote:
> However, the following works fine:
>
> <A href=
> "javascript:void(setTimeout('document.jmol.script(\'cpk 100%\')',1))"
> >spheres</a>
>
> That is, instead of issuing the .script() command directly, if the
JavaScript
> starts a new thread with a 1 millisecond delay that executes the script,
then all is well.
What a disaster.
I will start an off-list email thread with Steven Michaud, author of the
Mac OS X javaplugin. He (obviously) has quite a bit of experience with the
LiveConnect implementation on the Mozilla browsers, so he may be able to
shed some light on it.
> If possible, we should figure out what is happening and
> fix it from within Jmol.
I think that we need to eliminate the callbacks. I realize that I have
been preaching that for a long time ... and have yet to come up with an
alternate implementation.
> Was there a change in the way Jmol returns values with
> the script() command? I know I was suggesting a change there.
I do not recall making any changes. The script command has always returned
"void".
But the way that the 'callback' functions work could easily have changed.
> Starting new threads with setTimeout() can really be a headache.
Clearly.
Miguel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Jmol-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
