VisTrails too much action are saved in the undo stack when navigating to open a file
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
I'm noticing some odd behavior when loading files as it pertains to the UndoStack. When I click File->Open, several UndoSets are pushed onto the UndoStack with the label "Changed 'vtkSMProxy'". Then, as I change directories in the open file dialog, more UndoSets with the same label are created, and the render window seems to blink in and out a few times. After selecting a file, one UndoSet with label "Create 'Reader'" is created. This results in users being able to hit undo several times, once for each "Changed 'vtkSMProxy'" UndoSet that was created, without having any noticeable affect on ParaView.
However, if I load a file using File->Recent Files, none of those "Changed 'vtkSMProxy'" UndoSets are pushed onto the stack, and our VisTrail plugin handles this easily. I'm thinking all of those "Changed 'vtkSMProxy'" should either be combined into the "Create 'Reader'" UndoSet, or excluded altogether. This could be achieved by placing UndoSet exclude statements, or begin and end UndoSet statements around the code in pqLoadDataReaction.cxx.