the [1] there is not an atom number. It's just atomIndex + 1. (Because [0]
means last element in this scripting language.)
But just about all of these are now much more efficiently retrieved using,
for example:
jmolEvaluate({atomindex=1}.color)
On Tue, Feb 16, 2010 at 8:54 PM, Otis
Bob-
Thanks. I see the relationship from the atomInfo data now. I missed it
before.
I guess that I need to change to jmol.js, but doing so is going to bring
down my house of cards!
Otis
On Wed, Feb 17, 2010 at 9:24 AM, Robert Hanson hans...@stolaf.edu wrote:
the [1] there is not an atom
On Wed, Feb 17, 2010 at 9:03 AM, Otis Rothenberger o...@chemagic.comwrote:
Bob-
I guess that I need to change to jmol.js, but doing so is going to bring
down my house of cards!
No, no. Not at all. You can do anything you are doing now as well. It just
makes everything you are doing easier.
Ok, I did it. Very little in the page is broken. The only apparent break is
MSIE, and that's because under my boiler plate cross browser object embed I
had to use a convoluted dual object naming approach - i.e. even number
suffixes to MSIE and odd number suffixes to every other browser - don't
right. Typically you just leave that blank and it is jmolApplet0 (no caps
on jmol there) and you never have to worry about it.
On Wed, Feb 17, 2010 at 10:51 AM, Otis Rothenberger o...@chemagic.comwrote:
Ok, I did it. Very little in the page is broken. The only apparent break is
MSIE, and
Hello-
I have been getting atom properties by atom number:
e.g.
document.getElementById(appletID).getPropertyAsString(atomInfo[1].color)
I am working with some script issues that force me to get atom properties by
atomIndex. Is there any way to use atomIndex as the atomInfo array index?
I've
6 matches
Mail list logo
