Bug 512528

Summary: Editor state kept in memory indefinitely
Product: [Applications] KleverNotes Reporter: mdavidsaver
Component: UIAssignee: Louis Schul <schul9louis>
Status: REPORTED ---    
Severity: wishlist    
Priority: NOR    
Version First Reported In: 1.2.2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description mdavidsaver 2025-11-23 20:21:05 UTC 
SUMMARY

It appears that changes to the active note are in some situations kept in memory indefinitely, leaving them vulnerable to loss in the event of a crash (system or app).  I see that changes are flushed to disk when switching note.  I wish that edits were also flushed on a timer.  It would also be helpful to have some GUI indication when changes have not yet been written.

The logic for this might be to write to disk 3 seconds after the last change.  Start, or restart, a timer on each change.  Write to disk on expiration.  So changes are written after the user stop typing for awhile.

Or there is also the good old fashioned Save button.  I have been using kwrite/kate for note taking, so like many others, I am conditioned to reflexively `Ctrl+s`.

STEPS TO REPRODUCE
1. Create a new app.
2. Observe a zero length file appear on disk
3. Type some content
4. Wait 1 minute

OBSERVED RESULT

Still a zero length file.

EXPECTED RESULT

Not zero length file, containing changes shown in editor.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 13