After extensive editing of a very large ms for almost two hours, SEW 9.0 was terminated by Malware Bytes 4.3.0, which identified it as ransomware. It was easy to “restore” SEW 9.0, but I thought you should know. It might have nothing to do with 9.0, also, since Malware Bytes took 2 hours to trigger. My guess is that some virtually random pattern in the many work-files of this doc may have suddenly matched a virus signature, but that’s only a wild guess.
Nothing was lost or corrupted, which is testimony to the constant saving and robustness of SEW document handling.
One minor issue did come to mind. When I reopened the document in SEW, the UI was in the now ancient state it had been in, hours ago, when I first began working. It appears that although documents are constantly saved, the state of the UI isn’t preserved until the document is closed. I would prefer that the UI state is saved periodically to better prepare for just this situation I encountered. Under some circumstances it could be very inconvenient, especially in a large document, for the current state of the tree and all the open chapters to be reverted. Just a thought, but it would add to the crash-proof qualities of SEW.