But that's the problem, Adam. We carefully track the changed event and we then set up a recovery version if it's changed. Setting up the recovery version overwrites the previous recovery version.

 

So here's the scenario: during processing, our background operation automatically saves a recovery version at periodic intervals. If the user shuts down his/her browser without saving, or if the power goes off, the user can easily get that recovery version by opening CE and selecting a menu option we provide.

 

However, if the user first clicks into the editor before selecting the recovery version menu item, the Changed event assumes a change has been made and saves the contents (which are empty) as the recovery version. When the user then tries to get the recovery version that s/he expects, it's not there because it's been overridden by the "changed" document.

 

So it's very important that the click event does not trigger the Changed event..

 

FredD