Radical Documentation
View on GitHub
release-1
release-1
  • Home
  • Presentation
    • AbstractViewModel
    • Conventions
      • Bootstrap Conventions
      • Runtime Conventions
      • Conventions override
    • Commands and DelegateCommand
    • IViewResolver
      • Default view behaviors
      • view life cycle events
        • Callback expectations
        • notify messages
    • Message broker MVVM built-in messages
    • Application boot process demystified
      • Application shutdown
      • Singleton applications
    • AbstractMementoViewModel
      • Simple ViewModel graphs
      • Collections and complex ViewModel graphs
    • Validation and Validation Services
  • UI Composition
    • UI Composition
      • Region content lifecycle
      • TabControl region
      • Create a custom region
  • Concepts
    • Inversion of Control
      • Castle Windsor
      • Autofac
      • Unity (v2 & v3)
      • Puzzle Container
    • Entities
      • Property System
    • Messaging and Message Broker
      • POCO messages
      • Standalone message handlers
    • Observers
      • PropertyObserver
      • MementoObserver
      • BrokerObserver
  • Memento
    • Change Tracking Service
      • MementoEntity and MementoEntityCollection
      • Handling change tracking:
        • Simple model
        • Collections
        • Complex objects graph
      • Atomic operations
      • Change Tracking Service API
      • Property Metadata for the ChangeTrackingService
      • Handling collection sync
  • Behaviors
    • DataGrid Behaviors
    • Password
    • Generic routed event handler to command behavior
    • Overlay adorner
      • Busy status manager
    • TextBox behaviors:
      • Command
      • Auto select
      • DisableUndoManager
  • Markup Extensions
    • Editor binding
    • Auto Command binding
  • How to
    • Get the view of a given view model
    • Bi-directional communication between different windows/views
    • Handle the busy status during async/long running operations
    • Implement a customer improvement program
    • Manage focus
    • Create a splash screen
    • Access view model after view is closed
    • Intercept ViewModels before it's used
Powered by GitBook
On this page
  1. Memento
  2. Change Tracking Service
  3. Handling change tracking:

Simple model

PreviousHandling change tracking:NextCollections

Last updated 5 years ago

We briefly introduced and seen a code snipped that allows us to attach the memento tracking system to an entity:

var memento = new ChangeTrackingService();

var person = new Person();
memento.Attach( person );

person.FirstName = "first name value";
person.LastName = "last name value";

var isChanged = memento.IsChanged; //true
var canUndo = memento.CanUndo; //true

What is happening is that each change performed on each tracked entity will be recorded by che ChangeTrackingService, on each tracked entity means that the following will work as expected:

var memento = new ChangeTrackingService();

var person = new Person();
var customer = new Customer();
memento.Attach( person );
memento.Attach( customer );

person.FirstName = "first name value";
person.LastName = "last name value";
customer.CompanyName = "sample company";

var isChanged = memento.IsChanged; //true
var canUndo = memento.CanUndo; //true

Tracking at the same time both the Person instance and the Customer instance. The following sample highlights how changes are tracked:

var memento = new ChangeTrackingService();

var person = new Person();
memento.Attach( person );

person.FirstName = "a name";
person.LastName = "last name";

var isChanged = memento.IsChanged;
var state = memento.GetEntityState( person );

memento.Undo();
var _lastNameAfterUndo = person.LastName; //null

memento.Redo();
var _lastNameAfterRedo = person.LastName; //"last name"

The memento keeps tracks of a stack of changes in the exact same order they happened to the tracked models, each time Undo() is called the last change in the stack will be reverted and moved into the forward changes stack allowing the caller to call Redo() in order to apply it once again.

Calling AcceptChanges() on a memento instance will flush all the recorded changes considering the models as unchanged. Calling RejectChanges() will revert all the tracked models to their original state, or to the state we called AcceptChanges() last time.

The same applies also to collections:

MementoEntity and MementoEntityCollection
Handling Change Tracking in collections