Dear all,

I've been having a lot of success with Jmol now that I've gotten over
the inital activation energy. Before I write a blog post recording
what I've done and posting some pictures, I thought I might ask a
raise a few questions about random things that I came up against.

(1) Slabs appear to cut through all models. It would be great if a
slab could just be applied to one model or the selected models. (Use
case: I want to see the whole ligand in the active site, but I need to
cut back the isosurface.)

(2) "slab set" appears to behave differently than documented. I didn't
expect the slab to move or reset when I issued the command "slab set",
but it appears to do so, although it then remains fixed while rotating
the molecule (as documented).

(3) It would be great to be able to print out three points in the
slab, so that I construct a plane myself using those points or select
all points on one side of the plane.

(4) Loading property data using {*}.property_d = load("myfile.txt")
worked fine in the applet. However, I couldn't get it to work in the
application, where I wanted to load a file from a different folder.
Surely the applet isn't restricted by security to particular folders?
Also, I wasn't sure how to test whether the data was actually loaded
correctly. "print property_d" doesn't appear to do anything useful
even when property_d contains information.

(5) At one point, I was trying to select the last molecule in a model.
I had to do something like:
   nMol = getProperty("moleculeInfo", {model=1.1}).size
and use,
  script INLINE "select molecule=" + nMol

Would something like "select molecule=-1" be a good idea?

(6) I found that mapping property data onto an isosurface worked fine
except that you need to have property data for every atom in every
model up to the model for which you are actually drawing the
isosurface. I think this is undocumented, and doesn't really seem to
be a useful feature. (The documentation just says that property data
is required for every atom in the model, which seems more reasonable.)

(7) jmolScriptWait is a good idea. But it'd be great to have something
similar for jmolInitialize, either a Wait version, or a callback to a
javascript function (e.g. onload="myfunction"). At the moment, I stuff
everything into the call to jmolInitialize, but it's not really the
best way to do it, and if I want to do some javascript to process some
feature of the model after it has been loaded, it's not very
convenient.

Let me know if you want some example pages, or if I should file
feature requests, etc.

Noel

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to