How does GRANITE handle undo and rollback deltas?
GRANITE provides two mechanisms for part rollback: feature suppression and undo. These facilities work together to enable high-performance modeling. Undo provides the ability to restore the state of the model to a previous state. Changes to each model can be undone and redone independently. Applications can set any number of marks on model and can undo and redo to those marks. Tracking a mark is as simple as holding a reference to it. Redo is supported by the same functions. Rollback is a different mechanism, normally used when suppressing a feature, which reverts geometry and topology changes made by a feature. Rollback information is also persisted with the model, which means saved models need not be regenerated when loaded.
Related Questions
- I dunno the specfics of rollback, but is it really all that different than using Undo, or a couple of the other ways of auto-reverting Ive seen?
- Is Automatic Undo Management compatible with existing applications or scripts designed to use rollback segments?
- How does GRANITE handle undo and rollback deltas?
