Changes between Initial Version and Version 1 of Ticket #4472


Ignore:
Timestamp:
2017-07-16T08:26:18Z (8 years ago)
Author:
massimo ceraolo
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4472 – Description

    initial v1  
    22OM version: alpha1 64 bit for windows.
    33
    4 In two occasions suddenly  file containing my models lost the majority of its contents, and, while the model tree was still visibile in the Model Browser, many models appeared empty when seen in Text View.
     4In two occasions suddenly the file containing my models lost the majority of its contents, and, while the model tree was still visible in the Model Browser, many models appeared empty when seen in Text View.
    55This is an awful event, since one looses everything written since the last time he copied his file to a safe place.
    66
    … …  
    1111Point 1). Maybe we could add a feature so that every time one saves a file, a twin file, e.g. with the extension "bak" is created with the previous version.
    1212
    13 Point 2) occurence of this event can be detected. In fact when a model name "MyModel" is present in the Libraries Browser, at least "model MyModel end MyModel;" should be present in the code. So if we try to view (e.g. in text view) a model whose name exists in Libraries Browser, and his code is empty, we understand that corruption has occurred. In this case we could display the dialog similar to the one we already have to send a crash report, to send a "corruption report". While this report is sent, the user can be prompted to check his files and the corresponding "bak" versions. The corruption report should contain useful info to replicate the corruption, and then to fix the issue.
     13Point 2) occurence of this event can be detected. In fact when a model name "MyModel" is present in the Libraries Browser, at least "model MyModel end MyModel;" should be present in the code. So if we try to view (e.g. in text view) a model whose name exists in Libraries Browser, and his code is empty, OMEdit can understand that corruption has occurred. In this case it could display the dialog similar to the one we already have to send a crash report, to send a "corruption report". While this report is sent, the user can be prompted to check his files and the corresponding "bak" versions. The corruption report should contain useful info to replicate the corruption, and then to fix the issue.
    1414