Add "Accept external changes" button for "The library has been modified by another program"

[mpatas]

When message "The library has been modified by another program" is shown (both when the BibTeX file has been modified by another program and when JabRef itself saves it and bug #4810 or #4877 comes into play), it comes with two buttons (as seen in descriptions of #4810 or #4877):

1. Dismiss changes
2. Review changes

However, there are three possibilities:

1. Use the version open in JabRef, rejecting external modifications
2. Use the version on the disk, accepting external modifications
3. Choose something else (maybe look at the changes first, maybe merge those versions in some way)

The first option seems to be covered by "Dismiss changes", the third option is covered by "Review changes", but it looks like nothing covers the second option (other than closing the program and running it again, which seems to be suboptimal).

So, perhaps adding a third button (let's say, "Reload from disk") to the message "The library has been modified by another program" would be a good idea?

[koppor]

I will first fix #4877 then we can come back to here.

Assume the "Review changes" functionality would work (which is our aim). Then the button "Reload from disk" would assume that the user blindly trusts the content on disk and his own changes will be overwritten?

I think, the issue is that the change detection is not working well. This can cause risk that "Reload from disk" destroys in-memory data - in the use case of a shared .bib file (e.g., dropbox, onedrive, ...)

This strongly refs #5669

[mpatas]

Assume the "Review changes" functionality would work (which is our aim). Then the button "Reload from disk" would assume that the user blindly trusts the content on disk and his own changes will be overwritten?

Sometimes the user does trust the content on disk, and does so for a good reason.

For example, that happens when the user was working on a different computer and has put a new version to the disk using FTP, Git, E-Mail or something else.

Sure, there are other cases when pressing such a button would be a bad idea, which is a good reason for having three buttons and not one.

But, of course, such a button would be less important, if the changes of files are going to be detected correctly.

[OlafKleinBerlin]

I would like to suggest to point out in the choices which one will dismiss the changes one had done in Jabref and which one will dismiss the one changes according to the changed file.

[NYH-Dolphin]

Hi, I am a junior student and now I am learning software engineering. I have read your development documentation https://devdocs.jabref.org/contributing.
I am wondering whether I can try to solve this problem. Am I the first person who proposed to solve this problem?

[koppor]

@NYH-Dolphin I am working on the underlying issue (as written at #8235 (comment)). This issue is about the UI.

The issue is about having three buttons when a change on the disk occurred:

• Use the opened version (currently "Dismiss changes"; already exiting)
• Use the version on the disk (currently not existing)
• Review changes (already existing)

The main challenge will be the localization. - Jsut go ahead!

[NYH-Dolphin]

Hi Jabref, I am trying to fix this issue now. I am wondering whether [Accept Changes] need to automatically save the modified file? This need to call the variable of SaveDatabaseAction in the DatabaseChangeMonitor class. I am not sure whether I have break the calling rules?

This is the part that I am trying to modify

In order to implement this function, I have to pass the LibarayTab parameter instead of LibraryTab.DatabaseNotification class.

So the parameters passed are just like this

[NYH-Dolphin]

Now when Jabref detects the violation, it will display a dialogue like this

When you click [Accept changes], it will quickly show the changes and save it automatically

[DesBw]

Is it possible to make [accept external changes] automatic?
One can set it to always accept external changes: like in Texstudio.