#13 jmol - thread issues

closed
nobody
None
5
2006-04-06
2006-02-01
Andreas Prlic
No

Hi!

- I recently submitted a patch to the mailing list
about the threading issues related to the Eval of
scripting commands. The patch was not sufficient as
there still was an issue e.g. with the zap command. To
work around this, this patch provides an additional
evalStringSync method, which runs Eval in the main
thread, instead of starting a new one.

- the getAtomChain and getAtomSequenceCode of the
viewer are made accessible to the outside, so
applications do not have to parse the string returned
from notifyAtomPicked.

Discussion

  • Andreas Prlic
    Andreas Prlic
    2006-02-01

    a cvs diff

     
    Attachments
  • Bob Hanson
    Bob Hanson
    2006-03-07

    • assigned_to: nobody --> hansonr
    • status: open --> closed
     
  • Bob Hanson
    Bob Hanson
    2006-03-07

    Logged In: YES
    user_id=1082841

    the command is being implemented as

    String evalStringWait(String script)

    getProperty("jmolStatus","atomPicked")

    returns more friendly information.

    your patch is certainly more involved; please try
    what I have implemented and see if it does the trick for
    you. No script queue was implemented; not sure where that
    idea is necessary.

     
  • Andreas Prlic
    Andreas Prlic
    2006-04-06

    • assigned_to: hansonr --> nobody
     
  • Andreas Prlic
    Andreas Prlic
    2006-04-06

    Logged In: YES
    user_id=1441570

    Hi Bob,

    I checked out the current version from SVN, but
    JmolSimpleViewer does not contain an evalStringWait method.

    I suppose it would work like:

    viewer.evalStringWait("select *.B; spacefill on; ");
    viewer.evalStringWait("select *.A; wireframe on; ");

    ?

    Thanks,
    Andreas