9 Sep 2014, 2:58, Robert Hanson wrote:
In addition to that, the chain read from then HELIX record was not
stored the same way, so helixes and sheets were not read for any
chain that was outside the range A - Z.
Partly solved, but with another glitch now present:
in 14.3.7_2014.09.08b
Right - I forgot to do a full clean before creating the JAR file. Oh, I
hate that bug in Eclipse
Will update again now.
On Mon, Sep 15, 2014 at 8:52 AM, Angel Herráez angel.herr...@uah.es wrote:
9 Sep 2014, 2:58, Robert Hanson wrote:
In addition to that, the chain read from then HELIX
http://chemapps.stolaf.edu/jmol/zip/jmol-14.3.7_2014.09.15b.zip
On Mon, Sep 15, 2014 at 9:58 AM, Robert Hanson hans...@stolaf.edu wrote:
Right - I forgot to do a full clean before creating the JAR file. Oh, I
hate that bug in Eclipse
Will update again now.
On Mon, Sep 15, 2014 at
sorry, that's not Calpha-only
But the problem is present --now I don't know the reason
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version
This relates to the chain case issue as well. Jmol is set to force case
sensitivity if it finds (a) chain designations of more than one character
or (b) ones with lower case. Unfortunately, it was considering 1 to be
lower case.
In addition to that, the chain read from then HELIX record was not
