Re: [Jmol-users] try again (select)

2015-09-25 Thread Robert Hanson
I will look these over carefully. I think there are some inconsistencies that need reconciling. Bob -- ___ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.

Re: [Jmol-users] try again (select)

2015-09-25 Thread Rolf Huehne
On 09/25/2015 07:56 AM, Robert Hanson wrote: > Your keys are only "1" and "2" -- there are no "res" anythings at that > level. > Yes, because I thought the '**' was specially for searching at the second level. Wouldn't it be more consistent if it would be 'xxx*' (etc.) and not 'xxx**' when only t

Re: [Jmol-users] try again (select)

2015-09-24 Thread Robert Hanson
Your keys are only "1" and "2" -- there are no "res" anythings at that level. $ print selectTest("1** where resName='VAL'") { "1" : { "resName" : "VAL" "resNumber" : 1 "siteMembers" : [ { "resName" : "VAL" "resNumber" : 10 } {

Re: [Jmol-users] try again (select)

2015-09-24 Thread Rolf Huehne
On 09/16/2015 07:00 AM, Robert Hanson wrote: > new feature: JmolSQL {associative array}.select("xxx** where...") >-- double * indicates desire to return full sub-arrays, with keys >-- "all keys starting with "xxx"; >-- uses LIKE >-- can be at beginning or end or both: xxx**, **xxx,

Re: [Jmol-users] try again (local variables)

2015-09-23 Thread Rolf Huehne
On 09/23/2015 02:04 PM, Robert Hanson wrote: > First thought is that we should leave it this way. That is really really > bad programming. > Fixed. > Actually there is one case in Jmol where it is needed: If the loop variable is supposed to be part of an automatically actualized echo message. I

Re: [Jmol-users] try again (local variables)

2015-09-23 Thread Robert Hanson
(I was referring to the reuse of var i and global i; actually this was failing for any global) Will update later in the day. On Wed, Sep 23, 2015 at 7:04 AM, Robert Hanson wrote: > First thought is that we should leave it this way. That is really really > bad programming. > Fixed. > > On Wed,

Re: [Jmol-users] try again (local variables)

2015-09-23 Thread Robert Hanson
First thought is that we should leave it this way. That is really really bad programming. Fixed. On Wed, Sep 23, 2015 at 6:40 AM, Rolf Huehne wrote: > On 09/22/2015 07:33 PM, Robert Hanson wrote: > > http://chemapps.stolaf.edu/jmol/zip/jmol-14.3.16_2015.09.22.zip > > > > Jmol.___JmolVersion="1

Re: [Jmol-users] try again (local variables)

2015-09-23 Thread Rolf Huehne
On 09/22/2015 07:33 PM, Robert Hanson wrote: > http://chemapps.stolaf.edu/jmol/zip/jmol-14.3.16_2015.09.22.zip > > Jmol.___JmolVersion="14.3.16_2015.09.22" > > bug fix: for(var x in ...) does not respect "var" > Now a new global variable cannot be used in a 'for' loop: Example Code --

Re: [Jmol-users] try again (local variables)

2015-09-22 Thread Robert Hanson
http://chemapps.stolaf.edu/jmol/zip/jmol-14.3.16_2015.09.22.zip Jmol.___JmolVersion="14.3.16_2015.09.22" bug fix: for(var x in ...) does not respect "var" bug fix: x.format("JSON") fails for recursive x -- arrays or associative arrays can be recursive -- detection of recursion during SHOW, x

Re: [Jmol-users] try again (local variables)

2015-09-22 Thread Robert Hanson
Great test! ​This was a problem with the for(var x in...) not respecting the "var" -- ___ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/li

Re: [Jmol-users] try again (local variables)

2015-09-22 Thread Rolf Huehne
On 09/22/2015 03:46 AM, Robert Hanson wrote: > I think this is the essence of a deep copy: > > function deepCopy(a) { >switch (a.type) { >case "hash": > var b = {}; > for (var i = a.keys.length; i > 0; --i) { >var key = a.keys[i]; >b[key] = deepCopy(a[key]); >

Re: [Jmol-users] try again

2015-09-21 Thread Robert Hanson
Jmol.___JmolVersion="14.3.16_2015.09.21b" new feature: x = @a -- deep copy for a = array or associative array -- @a for string variable still gets the value of the variable named by variable a -- math environment only, not SELECT On Mon, Sep 21, 2015 at 8:46 PM, Robert Hanson wrote: > I

Re: [Jmol-users] try again

2015-09-21 Thread Robert Hanson
I think this is the essence of a deep copy: function deepCopy(a) { switch (a.type) { case "hash": var b = {}; for (var i = a.keys.length; i > 0; --i) { var key = a.keys[i]; b[key] = deepCopy(a[key]); } return b; case "array": var b = []; for (var j = a.le

Re: [Jmol-users] try again

2015-09-18 Thread Rolf Huehne
On 09/18/2015 04:38 PM, Robert Hanson wrote: > Oh, I mistyped. I did not mean to add that colon. > > Use of "*" and/or "," leads to copying, but we may want to rethink how that > works. *only that level* is copied. If there are references in there to > deeper levels, those levels are not copied. I

Re: [Jmol-users] try again

2015-09-18 Thread Robert Hanson
Oh, I mistyped. I did not mean to add that colon. Use of "*" and/or "," leads to copying, but we may want to rethink how that works. *only that level* is copied. If there are references in there to deeper levels, those levels are not copied. I have to think if there is a straightforward way to do

Re: [Jmol-users] try again

2015-09-18 Thread Robert Hanson
Hmm. Curious. I will check to see what is going on there. On Thu, Sep 17, 2015 at 9:11 AM, Rolf Huehne wrote: > On 09/16/2015 08:27 PM, Robert Hanson wrote: > > Use of "*:"or "," does result in copying. Use of the actual key does > not: > > > > $ x = { "b": 4,"a": 3,"d": { "d2": 4,"d1": },

Re: [Jmol-users] try again

2015-09-17 Thread Rolf Huehne
On 09/16/2015 08:27 PM, Robert Hanson wrote: > Use of "*:"or "," does result in copying. Use of the actual key does not: > > $ x = { "b": 4,"a": 3,"d": { "d2": 4,"d1": },"c": 5 } > $ y = x.d > $ y.d1 = 0 > $ print x.format("JSON") > > *{ "b": 4,"a": 3,"d": { "d2": 4,"d1": 0 },"c": 5 }* > $ y

Re: [Jmol-users] try again

2015-09-16 Thread Robert Hanson
Use of "*:"or "," does result in copying. Use of the actual key does not: $ x = { "b": 4,"a": 3,"d": { "d2": 4,"d1": },"c": 5 } $ y = x.d $ y.d1 = 0 $ print x.format("JSON") *{ "b": 4,"a": 3,"d": { "d2": 4,"d1": 0 },"c": 5 }* $ y = x.select("d,") $ y.d1 = -1 $ print x.format("JSON") *{ "b

Re: [Jmol-users] try again

2015-09-16 Thread Rolf Huehne
On 09/16/2015 07:00 AM, Robert Hanson wrote: > new feature: JmolSQL {associative array}.select("xxx** where...") >-- double * indicates desire to return full sub-arrays, with keys >-- "all keys starting with "xxx"; >-- uses LIKE >-- can be at beginning or end or both: xxx**, **xxx,

Re: [Jmol-users] try again

2015-09-16 Thread Robert Hanson
Hoooray! Some interesting issues there. JSME and 2D/3D - It turns out that JSME has two modes of delivery of SMILES -- "canonize" and "nocanonize". These are not dynamically switchable, as far as I can tell. I wish they were. The problem is that "canonize" delivers aromatic symbols for rings th

Re: [Jmol-users] try again

2015-09-16 Thread Robert Hanson
On Wed, Sep 16, 2015 at 8:09 AM, Paul PILLOT wrote: > > The only remaining glitch is in the test2.htm page that displays 2 still > images in the forefront, having the active molecule displayed ind the > background. > It appears on the two browsers I’ve checked. It doesn’t appear in any of > the o

Re: [Jmol-users] try again

2015-09-16 Thread Paul PILLOT
You’re right : jsmol.htm indeed works like a charm ! Paul > Le 16-09-2015 à 09:16, J. Bays a écrit : > > Paul: I think that is intentional. Try jsmol.htm. It is the same test without > > J. Philip Bays > Emeritus Professor of Chemistry > Saint Mary's Collegethe images. > Norte Dame, IN > > S

Re: [Jmol-users] try again

2015-09-16 Thread J. Bays
Paul: I think that is intentional. Try jsmol.htm. It is the same test without J. Philip Bays Emeritus Professor of Chemistry Saint Mary's Collegethe images. Norte Dame, IN Sent from my iPad On Sep 16, 2015, at 9:10 AM, Paul PILLOT wrote: Everything works as expected (including localization al

Re: [Jmol-users] try again

2015-09-16 Thread Paul PILLOT
Everything works as expected (including localization alerts, filter2D, fractional coordinates shorthand notation) ! Thanks a lot Bob ! The only remaining glitch is in the test2.htm page that displays 2 still images in the forefront, having the active molecule displayed ind the background. It app

Re: [Jmol-users] try again

2015-09-16 Thread Angel Herráez
simple.htm runs ok now here, without errors and the language is correct (it also was before) On 16 Sep 2015 at 0:00, Robert Hanson wrote: > http://sourceforge.net/projects/jmol/files/Jmol-beta/Jmol%2014.3/Jmol%2014.3.16/Jmol-14.3.16_ > 2015.09.15-binary.zip > > Jmol.___JmolVersion="14.3.16_2015

[Jmol-users] try again

2015-09-15 Thread Robert Hanson
http://sourceforge.net/projects/jmol/files/Jmol-beta/Jmol%2014.3/Jmol%2014.3.16/Jmol-14.3.16_2015.09.15-binary.zip Jmol.___JmolVersion="14.3.16_2015.09.15" bug fix: JSmol does not automatically start non-English language bug fix: JSME's noncanonical SMILES does not match Jmol's standard SMILES f