On 03/30/2015 03:31 PM, Robert Hanson wrote:
> Hmm. This is what I see:
>
> $ x = {}; x.updateDisplay = {}; x.caseTest = {}; print x
> {
> caseTest :
> {
> }
> updateDisplay :
> {
> }
> }
>
> $ x = {}; x..updateDisplay = {}; x..caseTest = {}; print x
> {
> caseTest :
> {
> }
> updateDisplay :
> {
> }
> }
>
> as expected.
>
>
> appletinfo.date "2015-03-27 20:40"
> appletinfo.version "14.3.13_2015.03.27"
>
In a freshly started Jmol I also don't see the problem.
But after it occured once it occurs reproducibly, independent of the
actual hash variable name.
I observed the same problem with other instances of Jmol and earlier
versions like 14.3.12_2015.03.01.
So it looks like some strange side effect...
...a few minutes later:
In the problematic Jmol instances there exists a user-defined function
'updateDisplay'. If I define one in a new instance I can now reproduce
the problem:
function updateDisplay(dummy) { print dummy }
Regards,
Rolf
--
Rolf Huehne
Postdoc
Leibniz Institute for Age Research - Fritz Lipmann Institute (FLI)
Beutenbergstrasse 11
07745 Jena, Germany
Phone: +49 3641 65 6205
Fax: +49 3641 65 6210
E-Mail: rhue...@fli-leibniz.de
Website: http://www.fli-leibniz.de
Scientific Director: Prof. Dr. K. Lenhard Rudolph
Head of Administration: Dr. Daniele Barthel
Chairman of Board of Trustees: Dennys Klein
VAT No: DE 153 925 464
Register of Associations: No. 230296, Amtsgericht Jena
Tax Number: 162/141/08228
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
