sure enough -- I forgot about that:
int val1 = vwr.getHermiteLevel();
val1 = (val1 <= 0 ? -val1 : vwr.getInMotion(true) ? 0 : val1);
Thus, hermite level is set to 0 only if the value is positive and the model
is in motion. But during spinning (which includes capture) we have;
public int getHermiteLevel() {
return (tm.spinOn ? 0 : g.hermiteLevel);
}
changing that to:
public int getHermiteLevel() {
return (tm.spinOn && g.hermiteLevel > 0 ? 0 : g.hermiteLevel);
}
does the trick. Thank's Angel!
Have released that as Jmol 14.6.0_2016.05.26, though it might also read
Jmol 14.6.0_2016.05.24 -- so I guess that is being overwritten. But it does
have this fix in it.
*Download Jmol-14.6.0_2016.05.24-binary.zip (66.4 MB)
<https://sourceforge.net/projects/jmol/files/latest/download?source=files>*
Bob
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
