Great, thanks Bob!
On 28 September 2014 15:45, Robert Hanson <[email protected]> wrote:
> BS Viewer.getAllAtoms() will take care of that for you. Just AND that
> result with the bit set of atoms in question, and it will limit that set of
> atoms to only those that are not deleted.
>
> Bob
>
>
>
> On Sun, Sep 28, 2014 at 6:33 AM, N David Brown <[email protected]> wrote:
>
>> Ok thanks Bob.
>>
>> Is there a way to identify programmatically that the atoms have been
>> deleted, besides simply listening for delete commands?
>>
>> On 28 September 2014 04:27, Robert Hanson <[email protected]> wrote:
>>
>>> Deleted atoms are marked deleted, but they are not removed from the
>>> model. Only when you delete a whole model using *zap 1.1*, for example.
>>> are the atoms for a model actually removed from memory.
>>>
>>>
>>
>>
>
>
> --
> Robert M. Hanson
> Larson-Anderson Professor of Chemistry
> Chair, Department 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
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
