G'day,

I'm upgrading our site's installation of JmolApplet from v10.0.0.42 to 
v11.6.1 (we want to render Mopac data).

In the main there have been no problems.  However, when it comes to PDB 
data containing multiple models Jmol v11.6 displays the error message:

"No atoms found for file string type pdb"

I don't use the JavaScript library to generate the Jmol applet tag, 
preferring to have the server to render the applet tag directly.  Thus, 
the applet tag looks something like,

<object
   classid="java:JmolApplet"
   codetype="application/x-java-applet;version=1.4.2"
   height="600"
   width="800">
   <param name="cache_archive" value="JmolApplet.jar">
   <param name="cache_version" value="11.6.1.0">
   <param name="codebase" value="http://solstice-v1.rt.intra:8000/java";>
   <param name="codebase_lookup" value="false">
   <param name="image" value="">
   <param name="loadInline" value="Multiple model PDB data with |
used as line-separator"
   <param name="script" value="model all">
</object>

This worked fine under Jmol v10.  Additionally, single-model PDB data 
loads fine with v11.6.

I've tried removing the "script" parameter but get the same result.

Searching for the "no atoms found" error message lead me to this posting:

http://www.mail-archive.com/[email protected]/msg09043.html

but the problem there is caused by Jaguar files and the | character.

Any suggestions on how to use the loadInline and script parameters to 
render multi-model PDB data with v11.6 would be greatly appreciated.

Thanks,
Chris.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to