Changes between Version 5 and Version 6 of Notifications

Timestamp:

Jun 19, 2015, 5:19:31 PM (10 years ago)

Author:

Eric Pettersen

Comment:

--

Notifications

@@ -14 +14 @@
 == Data Changes
 
-Again, this will be similar in many ways to Chimera 1.  Changing the color of an Atom will put that Atom in the "modified" set of Atoms and add "color changed" to the list of Atom reasons.  A significant difference from Chimera 1 is that instead of firing individual Atom/Residue/Chain/etc. triggers, one "atomic data" trigger will fire whose associated data is a dictionary that has keys of Atom/Residue/Chain/etc. and values that contain the reasons, the sets of create/modified items, and possibly the set of deleted items.  This eliminates timing issues of which trigger should fire first and eliminates the possibility of changes by trigger handlers "infiltrating" later single-class triggers.  Such changes will instead accumulate into the next firing of the atomic-data trigger.
+Again, this will be similar in many ways to Chimera 1.  Changing the color of an Atom will put that Atom in the "modified" set of Atoms and add "color changed" to the list of Atom reasons.  A significant difference from Chimera 1 is that instead of firing individual !Atom/Residue/Chain/etc. triggers, one "atomic data" trigger will fire whose associated data is a dictionary that has keys of !Atom/Residue/Chain/etc. and values that contain the reasons, the sets of create/modified items, and possibly the set of deleted items.  This eliminates timing issues of which trigger should fire first and eliminates the possibility of changes by trigger handlers "infiltrating" later single-class triggers.  Such changes will instead accumulate into the next firing of the atomic-data trigger.
 
 The atomic-data trigger will fire when no user/tool code is executing, though like Chimera 1's checkForChanges() it will be possible to explicitly force the trigger to fire if needed.