<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16788" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Angel,</DIV>
<DIV>Thanks for stating this again. I think that I am beginning to understand more fully what is happening when saving a scene. Running commands through the console and then saving the scene is not as simple and straight forward as I thought.</DIV>
<DIV> </DIV>
<DIV>Karl<BR><BR>>>> "Angel Herraez" <angel.herraez@uah.es> 2/2/2009 10:38 AM >>><BR>Hi Karl <BR><BR>I think what is happening is that the PP authoring environment saves <BR>Jmol states for the scenes / green links. These states do not contain <BR>the script history, but the current state of the model. So, even if <BR>you load the isosurface from file, the state will contain the full <BR>isosurface generation command. This is by design: Jmol state scripts <BR>are made to reproduce the current state of the model without any <BR>other data required.<BR><BR>The only solution I see is the possibility to edit (even manually) <BR>the script saved by the PP-SAT in the server: remove the isosurface <BR>calculation and substitute with the isosurface load-from-file.<BR>This process could conceivable be automated incorporating it into the <BR>surface part of the SAT, but I see it quite difficult to implement <BR>safely.<BR><BR><BR>________________________________
_______________<BR>Proteopedialist-for-users mailing list<BR>Proteopedialist-for-users@bioinformatics.org<BR><A href="http://www.bioinformatics.org/mailman/listinfo/proteopedialist">http://www.bioinformatics.org/mailman/listinfo/proteopedialist</A>-for-users<BR></DIV></BODY></HTML>