Re: [Jmol-users] set shadow

[Bob H. <ha...@st...>]

Sérgio Ceroni da Silva wrote:

>Bob Hanson escreveu:
>  
>
>>Sérgio Ceroni da Silva wrote:
>>Hi everybody
>>Today I found out that some old scripts were misbehaving with the latest (11.4.RC2) Jmol (can't tell when it started). The command "set shadow off" was the culprit (many commands stop responding after a "set shadow"). It appears that this Rasmol/Chime command was never implemented (could find only a few discussions dating back to 2004 on the mailing lists). Strangely, only recent Jmol versions started to show this behaviour.
>>Regards
>>Sérgio
>>
>>  
>>    
>>
>>>That's because we made "set" function only with implemented Jmol 
>>>parameters. So really this is a GOOD thing -- that it is indicating 
>>>properly that "set shadow" doesn't exist
>>>      
>>>
>I was just reporting that I would expect 
>for Jmol to ignore it and carry on with the remaining valid instructions 
>in the script instead of the odd behaviour I've seen. Thought could be a 
>symptom worth reporting, since an invalid command is affecting several 
>other valid ones that follow in the script. Should this really be expected?
>  
>
Whether or not it is expected, I'm just saying that the current behavior 
is probably better than the previous in that now you can find the points 
in your old Chime scripts that should be modified to run properly in 
Jmol. "set shadow" is fairly superficial, but there could be other Chime 
settings that are more critical. As it was, your script might silently 
malfunction; now you get to find out exactly what in Chime is not 
implemented in Jmol.

If you would like to have a setting that ignores SET variable errors, 
that would be easy to implement.

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