From: Robert H. <ha...@st...> - 2011-02-07 13:10:48
|
thanks -- that's fixed. Not sure how that got lost. It's fixed in 12.1.34 and 12.0.31, which I hope Nico can release later today. On Fri, Feb 4, 2011 at 4:51 PM, Oliver Stueker < rev...@us...> wrote: > Hi, > > I just noticed that the element assignment via atom properties is > broken in Jmol 12.0.30: > > {*.?H??}.element=1 ; # fails > {*.?H??}.element="H" ; # fails > > while it still works for individual atoms: > > {atomno=2734}.element=1 ; # works > > In Jmol 12.0.28 it still worked. > > > Oliver > > > ------------------------------------------------------------------------------ > The modern datacenter depends on network connectivity to access resources > and provide services. The best practices for maximizing a physical server's > connectivity to a physical network are well understood - see how these > rules translate into the virtual world? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > Jmol-users mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-users > -- Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 507-786-3107 If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |