Hi,

There are no such plans - selecting a node modifies the diagram xml since selection state is saved too. You could implement your own modification tracking instead by setting a flag from Created/Modified/Deleted event handlers.

I hope that helps,
Stoyan

I just run into this same issue. Implemented change detection using the Dirty property and DirtyChanged event only to find it's a bit over keen.

It would be nice if the excellent help on these forums made it into the help though. If the help had been a bit clearer that selecting etc also set the flag it would have saved some time.

However I'd like to also point out its not as easy as just handling the Node and Link Created/Modified/Deleted event handlers. There are extra ones such as LinkTextEdited that need to be considered. Also I just found out they aren't raised for code added nodes or link text changes.

So although its easy enough in the end it you have to be really careful your catching all places.

I would have been nice if there was a DirtyChanging event that had an argument saying what was changing and could be cancelled (say for selecting)

Not a big issue, but it has taken a few hours more than I had thought it would, but at least this control has all the events etc needed to do it manually (not something can be said about all controls)

For anyone who stumbles on this thread, here's my kludgy "solution" for avoiding the "dirty" flag getting set when the user selects a node:

      // Copy of the "dirty flag", saved when the Diagram.NodeSelecting event was fired, and a time
      //  stamp as a kludge solution of detecting if this is happening
      private bool _savedDirtyFlag = false;
      private int _nodeSelectionTimestamp = 0;

   ...


      // Following two event handlers are used to suppress MindFusion's setting of the "dirty flag"
      // for just selecting a node.

      private void Diagram_NodeSelecting(object sender, NodeValidationEventArgs e)
      {
         _savedDirtyFlag = _diagramView.Diagram.Dirty;
         _nodeSelectionTimestamp = Environment.TickCount;
      }

      private void Diagram_DirtyChanged(object sender, EventArgs e)
      {
         if (Environment.TickCount - _nodeSelectionTimestamp < 100)  // 100 ms.
            _diagramView.Diagram.Dirty = _savedDirtyFlag;
      } 

And to be consistent with my principle that selection should not be considered to be a part of the Diagram object that should be persisted, I deselect everything before saving the diagram:

            List<DiagramItem> savedSelection =
                                      new List<DiagramItem>(_diagramView.Diagram.Selection.Items);
            _diagramView.Diagram.Selection.Clear();

            _diagramView.Diagram.SaveToStream(memoryStream, true);

            foreach (DiagramItem diagramItem in savedSelection)
               _diagramView.Diagram.Selection.AddItem(diagramItem); 

(I know that it would be simpler to just deselect everything after loading a saved diagram, but this somehow seems to be more correct.)

On reflection, I think the best solution would be for MindFusion to add a "selection should be persisted" option, and when that option is set to false then
a) changes in selection do not turn the dirty flag on
b) saving the Diagram object should not save selection info

Sounds good, great service, thank you.