Posted 19 years ago
by Boyd
-
Sr. Software Developer,
Patterson Consulting, LLC
The 'ModifiedChanged' event appears to reset itself inappropriately after an 'Undo' operation.
1) Open Sample Application
2) Insert a blank line (Notice the event displayed in the console that Document.Modified = 'True')
3) Save the file as anything. At this point, the 'Document.Modified' property should be 'False'.
4) Undo the operation from step 2. Our recently saved document has now been modified from it's saved state, but the console window displays 'Document.Modified = False')
This chain of logic as long as we don't save the document. When we save the document, it should reset the 'Modified' state. Even if I programmatically set 'Document.Modifed = False' after Step 3, I can't prevent this situation from happening.
Is there a way to "reset" the internal handling of modified states to create a new baseline for the undo operations?
1) Open Sample Application
2) Insert a blank line (Notice the event displayed in the console that Document.Modified = 'True')
3) Save the file as anything. At this point, the 'Document.Modified' property should be 'False'.
4) Undo the operation from step 2. Our recently saved document has now been modified from it's saved state, but the console window displays 'Document.Modified = False')
This chain of logic as long as we don't save the document. When we save the document, it should reset the 'Modified' state. Even if I programmatically set 'Document.Modifed = False' after Step 3, I can't prevent this situation from happening.
Is there a way to "reset" the internal handling of modified states to create a new baseline for the undo operations?
