Parameters Class about pluginplay HOT 1 CLOSED

One thing not covered by the purposed API is tracking changes. For all intents and purposes the purposed flow is:

1. ModuleLoader provides the original, documented, and version controlled default set of parameters to the ModuleManager.
2. The user gets the instance stored by the ModuleManager and changes them as appropriate for what they are trying to do.

Behind the scenes, between steps 1 and 2 I'd like to call a function, say, track_changes, which flips an internal flag indicating that from this point forward all modifications to the Parameters instance should be noted (specifically at a later point it would be useful to get a list of all entries for which change has been called after the call to track_changes). Multiple calls to track_changes should have no effect (the ModuleManager will always call it and developers may or may not).

from pluginplay.