Bob wrote: > I can imagine that if you have restricted > sets or otherwise "turned off atoms" > and there are lots of them (such as the way > Eric has mentioned turning off > different models) the user could be in for a > surprise if they run a monitor to > an atom that isn't there.
You cannot draw a monitor to an atom that is not there. An atom is *there* if a user could figure out where it was by looking at it on the screen ... if one or the following is true: - it has a non-zero spacefill value - it has a non-zero star value - it has at least one bond drawn to it > But if this is only > activated by the monitor > command itself, and not by user clicking, > then it should be fine to be able to do it. OK > Imagine you have several models and you want > to compare similar distances. > Shouldn't you just be able to turn on and > off display of the models and have the > monitors go on and off with them? > Or do the monitors stay, even though the > model is not visible? That's it! That is the problem. The reason that my 'hacks' for visibility tests were put in was to try to determine when monitors should be drawn. The problem is ... people build animations that have multiple models with measurements in each model. Measuremens currently do not have a mechanism to tell which model they are associated with. In fact, the problem is a little complicated because one can have a measurement that includes atoms from multiple models. I will need to think about this for a little while to try to come up with a scheme that handles all (most?) cases. Miguel ------------------------------------------------------- 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
