Hi Bob,
Thanks for the reply (not sure how best to thread the response, as I only get a
digest, and didn't get an individual email).
I think our problem is one of thread timing.
If I step through in the debugger it works fine, if I let it run it doesn't.
Currently Jalview closes down Jmol with:
viewer.acm.setModeMouse(JC.MOUSE_NONE);
viewer.evalStringQuiet("zap");
viewer.setJmolStatusListener(null);
As I understand it, "zap" actions include restarting the HoverWatcherThread. So
this isn't sufficient for shutdown.
So I tried adding...
viewer.startHoverWatcher(false);
viewer.dispose();
However I strongly suspect that we have problems when viewer.dispose() executes
before the script thread has had a chance to evaluate "zap".
This means we null the HoverWatcherThread _before_ the zap happens, and it
starts it up again.
Then the next time we open the Jmol viewer (with JmolViewer.allocateViewer())
we get a new one, and so on.
However if I reduce this all down to just
viewer.dispose()
it seems to behave ok. Does that sound ok?
Thanks,
Mungo Carstairs
Jalview Computational Scientist
The Barton Group
Division of Computational Biology
School of Life Sciences
University of Dundee, Dundee, Scotland, UK.
www.jalview.org<http://www.jalview.org/>
www.compbio.dundee.ac.uk<http://www.compbio.dundee.ac.uk/>
The University of Dundee is a registered Scottish Charity, No: SC015096
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
