Miguel wrote:
Eric wrote:
I found that if I did
monitor 200 201
no line appeared, until I spacefilled the monitored atoms. [snip]
Bob & Miguel wrote:
please report this as a bug. Clearly monitor should not
depend upon there being spacefilled atoms.
Agreed ... it is a bug.
In investigating this I see that my code is explicitly checking to see
that the atoms involved are *visible* ... where visible means that either
the atoms themselves have some screen representation OR there are bonds
that clearly indicate where the atom would be.
I am doing the testing for distances, angles, and torsion angles.
I do not remember why this test was put there. And my current thinking is
that it should be removed.
However, the code was clearly it was put there for a particular reason. So
that makes me wonder why.
Q: Can anyone think of any reason why I would have written code to turn
off measurements if all of the atoms involved in the measurement are not
visible?
I don't know.
I think that a restrict command should turn off monitor lines as it is
the case with bonds (wireframe) and it shouldn't be possible to generate
monitor lines between atoms that are not visible by *mouse* picking,
using a script command to turn on monitor lines may be possible.
Regards, Jan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
