Changes between Version 22 and Version 23 of ChimeraAnimationTasks


Ignore:
Timestamp:
Dec 23, 2010, 2:05:51 PM (15 years ago)
Author:
Darren Weber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ChimeraAnimationTasks

    v22 v23  
    1414=== Integrity Checking ===
    1515
    16 Take a look at the code for {{{chimera.update.checkForChanges()}}}.  This may be helpful in checking the validity of state parameters and in automatically detecting changes for transitions.
     16Take a look at the code for {{{chimera.update.checkForChanges()}}}.  This is related to c++ notification to python of object changes (using a 'modified atoms' list and another 'modified reasons' list).  This may be helpful in checking the validity of state parameters and in automatically detecting changes for transitions.
    1717
    1818Also, {{{chimera.openModels.addRemoveHandler(func, data)}}} might be used to add a trigger handler when removing models.  This might be useful in the creation of a state instance as a way to maintain integrity or validity of the saved state.  It may depend on whether the state instance keeps a reference or a copy of models in the saved state.  For efficiency, it is better to keep a reference.  For validity, it could be better to keep a copy.  Perhaps a copy is required only when a model is removed, so the copy action could be triggered then.  If a state instance that is registered as a handler is deleted, then call {{{chimera.openModels.deleteRemoveHandler(handler)}}} to delete the trigger handler.