<div dir="ltr"><div>That's indeed the concern of the autosave method.</div><div>Thanks for letting me know.</div><div>About your concern, I provide my suggestion as follows:</div><div><br></div><div>> Drawback would be that it is unusual and unexpected for many users (unless the</div>> user explicitly configured it that way).<div><p>The autosave function is disabled by default. Once the user clicks the button to turn it on, changes will be saved automatically. This ensures that users are aware they are in autosave mode. Additionally, autosave will remain enabled the next time the user opens Okular.</p><p>Does implementing the method this way make more sense? Feel free to let me know.</p></div><div>> If changes are saved automatically, you can’t use the file the next time</div>> anymore, because it is already filled.<div><p>In this situation, I suggest saving a backup file whenever the user closes Okular. This would create a list of backup files in a folder located in the same directory as the document. Users would then be able to roll back by checking different versions of the backup files.</p><p>To my understanding, the current policy in Okular does not allow users to revert to the original version of a file once they have saved it manually, right? Please correct me if I am mistaken. Thanks.</p><div><br></div><div>Best,</div><div>Wen<br><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><<a href="mailto:okular-devel-request@kde.org">okular-devel-request@kde.org</a>> 於 2024年7月17日 週三 下午7:00寫道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Okular-devel mailing list submissions to<br>
<a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:okular-devel-owner@kde.org" target="_blank">okular-devel-owner@kde.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Okular-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Add autosave function to Okular (Laura David Hurka)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 17 Jul 2024 07:26:20 +0200<br>
From: Laura David Hurka <<a href="mailto:laura.stern@mailbox.org" target="_blank">laura.stern@mailbox.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: Re: Add autosave function to Okular<br>
Message-ID: <6009722.DvuYhMxLoT@doro><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Wed, 17 Jul 2024 11:01:53 +0800 Wen Chang wrote:<br>
> I can do it that way by saving the changes in a backup file.<br>
> <br>
> I would like to know why modifying the file on disk without user<br>
> interaction is a bad idea based on your experience.<br>
> <br>
> Also, I noticed that VSCode automatically saves changes once they are made.<br>
> To my knowledge, only the file that the user is working on will be modified.<br>
> <br>
> What drawbacks would there be if a file is directly modified without user<br>
> interaction?<br>
<br>
Drawback would be that it is unusual and unexpected for many users (unless the <br>
user explicitly configured it that way).<br>
<br>
Imagine you have a form that you need to fill out often, and then just print <br>
once.<br>
If changes are saved automatically, you can’t use the file the next time <br>
anymore, because it is already filled.<br>
<br>
It would also not make much sense with “Open...”, “Save”, and “Save As...”.<br>
<br>
Laura<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Okular-devel mailing list<br>
<a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Okular-devel Digest, Vol 214, Issue 22<br>
*********************************************<br>
</blockquote></div></div></div></div>