You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please have a look to the support pages of our website : http://m2doc.org/support/
Current behavior
When using the "M2Doc Interpreter" View in Eclipse, the template file of the generation may end up in an unmodifiable state. This makes iterating painful, as the view must be switched to another contextual generation everytime we want to take into account recent changes in the template.
Moreover, closing the "M2Doc Interpreter" View does not always unlock the template file. In that case, restarting Eclipse is necessary to clear the locks.
Expected behavior
The "M2Doc Interpreter" View in Eclipse should not lock the template file for modifications, as it will only ever read from the file, and never write to it.
Closing the "M2Doc Interpreter" View should make sure it releases all locks taken on the template file.
Minimal reproduction of the problem with instructions
In the workspace, import the example project IFE with M2Doc
Open the "M2Doc Interpreter" View on the "Template SA Complete.genconf" generation.
Through the file system, open file "Template SA Complete.docx" in Word.
Edit it and save the file. Word 2019 has you believe the file is now saved.
Close the file: a dialog ask whether you want to save your document or not.
"Save" closes Word and re-opens it with your modifications still there
"Do not save" closes Word.
If you open the document, you can see that your changes were in fact not saved.
Close the "M2Doc Interpreter" View in Eclipse and open the template file.
Try to modify and save the template: you end up in the same situation a previously, as the lock on the file was actually not released. Re-opening the View to change the contextual generation does not fix that situation.
Closing Eclipse clears the locks.
What is the motivation / use case for changing the behavior?
Editing the template only in the Eclipse-embedded Word window is not always practical.
I'm submitting a...
Current behavior
When using the "M2Doc Interpreter" View in Eclipse, the template file of the generation may end up in an unmodifiable state. This makes iterating painful, as the view must be switched to another contextual generation everytime we want to take into account recent changes in the template.
Moreover, closing the "M2Doc Interpreter" View does not always unlock the template file. In that case, restarting Eclipse is necessary to clear the locks.
Expected behavior
The "M2Doc Interpreter" View in Eclipse should not lock the template file for modifications, as it will only ever read from the file, and never write to it.
Closing the "M2Doc Interpreter" View should make sure it releases all locks taken on the template file.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Editing the template only in the Eclipse-embedded Word window is not always practical.
Environment
The text was updated successfully, but these errors were encountered: