Hei,
i'm very new to this mailing list but i'm already enjoying the
atmosphere here !! Yes, the project is not that small but with the
good tools (jmol one of the most essentials) life is way
easier...again, if anyone wonna see the code send me a mail or wait
some days while i setup a SF account and manage CVS and the rest :)
Comments below >
>
> If you are using this method, they you are creating a Viewer object
> instead of a JmolViewer object. If something isn't in JmolViewer
> that you need, please let me know.
>
> I think what you really want there is a pickCallback. We could talk
> about that....
>
Got it, i'll take a look at pickCallback and maybe tomorrow will update you.
>
> steps 2.b(storing) and 2.e should not be necessary.
>
I'll try to explain better. When you do for example variable-cell
dynamics it may evetually happen that two subsequent configurations
are very different, reciprocal cell and atom positions. In that case i
thought it was better to do a complete refresh ( openStringInLine )
also beacuse in the code the refresh procedure (where the
openStringInLine is located) loads several new things used. In this
case the view is NOT conserved (at least in my jmol version...i'm
about to update to the cvs one), am i wrong ?
>
> The evalString() can be replaced with
>
> JmolViewer.script(String script);
>
Got it.
> This should be totally unnecessary. Jmol will be queuing the script
> commands.
>
I know...this was my home_made_threading_issue_solution....i know it's
pretty lame ;)
> There's your problem. Dont' mix openStringInline() with queued
> scripting. Just create a DATA command. That's what it is for.
>
> data "model x"\n
> xyzdatahere\n
> end "model x"\n
>
Ok, clear. But, after i load the configuration, i suppose i still can
interact with regular scripting. I mean, i can still add and remove
objects ? I'm sure yes...
>
> none of the public methods in Viewer are really "public" -- that is
> there only when other packages within Jmol are needing the method.
> The public methods are all in JmolViewer interface. Certainly I can
> add that (I just did -- see Jmol 11.7.46_dev) -- but you should
> think about using a pickCallBack method within a JmolStatusListener
> instead. See how that is done in Jmol.java.
>
> Bob
Clear, the best way is to implent pickCallBack, when it's done i'll
finally be a little more jmol-alike :))))))
I'll update as soon as i coded everything and i'll tell you the
improvements, sure are gonna be great ! Thanks a lot,
Riccardo
----------------------------------------------------------------
SISSA Webmail https://webmail.sissa.it/
Powered by Horde http://www.horde.org/
------------------------------------------------------------------------------
_______________________________________________
Jmol-developers mailing list
Jmol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-developers
