Sorry, that happened when I split off the user-defined variables from
the Jmol-standard variables. It's fixed; what you need to do is remove
the "=" sign from the line.
@~hprev "({0:65})";
Rolf Huehne wrote:
> Hi all,
>
>in Jmol 11.3.20 Jmol atom set definitions (e.g.: "define ~hprev
>selected") are included wrongly into the state script. When I reload a
>script I get the following kind of error message:
>
>@~hprev = "({0:65})";
>script ERROR: invalid argument
>----
> set @define >> ~hprev << "({0:65})"
>
>In Jmol 11.3.15 it still works and the corresponding state line looks
>like this:
>
>@~hprev ({0:65});
>
>This command still works in 11.3.20.
>And if the "@" at the beginning of the line produced by 11.3.20 is
>removed it also seems to work:
>
>~hprev = "({0:65})";
>
>
>
hmm. Interesting; I guess that's true.
>Regards,
>Rolf
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2005.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Jmol-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/jmol-users
>
>
--
Robert M. Hanson
Professor of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
