Review Request 118894: parley / libkdeedu : fix Bug 240552 - Second parley process cancels out changes in language file when closing

[Andreas Xavier]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118894/
-----------------------------------------------------------

(Updated June 23, 2014, 11:50 p.m.)


Status
------

This change has been marked as submitted.


Review request for KDE Edu.


Bugs: 240552
    http://bugs.kde.org/show_bug.cgi?id=240552


Repository: parley


Description
-------

This fixes the parley portions of the bug and is intended to work with https://git.reviewboard.kde.org/r/118686/

This patch introduces new strings before the string freeze and new functionality. The libkdeedu portion of the patch implements file locking, to prevent the data lose mentioned in the bug.  The new functionality in this patch is to allow the user to steal the lock.

The functionality is simple.  When the user tries to open a locked file a dialog pops up to explain the file lock, warn about data loss and ask the user if they wish to steal the lock.  If the user steals the lock, then the behavior is similar to before and the user will lose data if there are actually two processes running simultaneously.


New Bug:  There is a new bug.  On exit there is an intermittent crash.  I will fix this bug after the string freeze.  I think that it is caused by a change in the order of the teardown introduced by the new code.  

 


Diffs
-----

  src/parleydocument.h e3c099f 
  src/parleydocument.cpp 1681a93 
  src/parleymainwindow.cpp db8b5a8 

Diff: https://git.reviewboard.kde.org/r/118894/diff/


Testing
-------

It was difficult to create unittests as the gui functionality is split between parleydocument and mainwindow, so it is difficult to instrument.

I ran by hand 2 to 3 parley practice sessions.  I checked the xml file to determine if there was data loss.

There was never data loss if I didn't steal the lock.

Stealing the lock results in data loss when:
 - autosave is enabled
 - save on exit is enabled
 - the user saves the 2nd process after the 1st parley have closed the vocabulary.

All of these cases are better than the current version, as the user is notified that you will lose data if you steal the lock.


Thanks,

Andreas Xavier

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20140623/ce552466/attachment.html>