M
Microsoft
Is the order in which Visio sends events officially documented anywhere? I can use the Visio Event Monitor, or just write my own test Visio apps to reverse engineer the event sequences for a particular version of Visio. But, using this approach, I cannot be sure that I am actually catching all possible scenarios, or that the sequences will not change between versions of Visio. This is not a very comfortable situation, and event sequences should not be this be this opaque.
In particular, I am interested in the events that Visio sends when it does one of the following to a Visio document:
a.. Close
b.. Save
c.. SaveAs
d.. Copy to a mailfile
e.. Make an AutoRecover snapshot
The "Close" and "Save" scenarios can actually cause other events to occur. For instance, during a Close, Visio may detect a data change and attempt to do a Save. Also, during a Save, Visio may discover that there is no data file yet, and attempt to do a SaveAs.
Visio developers need to be given an official control flow diagram that shows what events are generated under what circumstances, so that we know exactly what events to look for, and also so we can feel comfortable that the flow control is unlikely to change between Visio versions. We should not be forced to make guesses, and hope that undocumented behavior does not change.
In particular, I am interested in the events that Visio sends when it does one of the following to a Visio document:
a.. Close
b.. Save
c.. SaveAs
d.. Copy to a mailfile
e.. Make an AutoRecover snapshot
The "Close" and "Save" scenarios can actually cause other events to occur. For instance, during a Close, Visio may detect a data change and attempt to do a Save. Also, during a Save, Visio may discover that there is no data file yet, and attempt to do a SaveAs.
Visio developers need to be given an official control flow diagram that shows what events are generated under what circumstances, so that we know exactly what events to look for, and also so we can feel comfortable that the flow control is unlikely to change between Visio versions. We should not be forced to make guesses, and hope that undocumented behavior does not change.