I would like feedback on the following possible change in the behavior of SET:
CURRENT: You can SET any variable, whether a Jmol standard varible or a variables you have created. SUGGESTED CHANGE (option 1): When you use SET, if the variable is not a Jmol variable, an error is thrown and the script fails. SUGGESTED CHANGE (option 2): When you use SET, if the variable is not a Jmol variable, a warning is thrown, but the script continues. RATIONALE: If you are setting a Jmol variable (debugScript, antialiasDisplay, etc.), it can be easy to mistype a name. The way it is now, Jmol happily assigns a new variable with that value. Suggested Change 1 makes it so that if you get in the habit of using SET (the way it was done in 10.2) for setting Jmol standard variables, then you will know immediately that you have mistyped a variable name, and no new variable will be created. Suggested Change 2 lets you know immediately, but the variable is still created. The idea here is that some people may have already created scripts using "set" and user variables. The problem with 2 is that upon mistyping, the Jmol state will contain that mistyped variable definition, because the command did complete. Thoughts? Bob -- 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: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
