BUG: PNotes Portable 4.0 - autosave - recovery of auto-saved note(s) fail after unclean shutdown, IF note has NOT been explicitly saved [yet].
First of all I'd like to take the opportunity to give my appreciation to the PNotes developer(s) for the quick response to my request for implementing an auto-save feature for non-saved notes only (thereby avoiding unnecessary writes/wear to a flash drive).
Background: I launch the PortableApps.com menu from a script, which is auto-launching some applications before launching the PortableApps.com menu and killing applications (e.g. PNotes Portable) that are still running on exit of the PortableApps.com menu.
Issue: Whilst testing I noticed that, if I create a new note that hasn't been explicitly saved when killing (using 'kill -KILL procid') PNotes Portable, the auto-saved message doesn't seem to be restored on the next start-up of PNotes Portable.
On the next start-up PNotes Portable reports: "Program did not finish correctly last time. Would you like to load auto-saved notes?". Despite responding "Yes" the auto-saved message seems to be lost. This is not the case IF the auto-saved message has been saved explicitly, at least once, before the auto-save was triggered after a modification.
BTW, what is the point in having to confirm the restoration of auto-saved messages, e.g. after an unclear shut-down? IMHO, at least in my world, notes are short messages (unlike e-mails, or documents) and thus shouldn't need to be saved explicitly at all. It's fine to provide an option for the user to require explicit saving of notes, but in my opinion it's more intuitive to auto-save new/modified notes by default instead.
JFYI, the "DefualtNote"'s title seems to be mispelt 
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I would say that killing the process would not activate the autosave. I dug around via the search feature, and found this: https://portableapps.com/node/12750#comment-79991; which I've copied below
I haven't been here for a few days - sorry for delay. The autosave DOES work on PNotes and I've just tested it. It's intended to prevent data loss on program or system crashes, i.e. it saves notes in temporary files and in case of crash will offer you to restore them when program starts. If the program ends in normal way, it will delete all temporary files on next start. Oh, yes, you should save the note at least once (no matter when) in order to allow it to be restored (may be this is a point for further working on - allow to restore just created but not save yet notes as well).
@The misspelling- it seem's I've failed on so many levels
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
Let me clarify somewhat about the killing thing. I don't expect PNotes auto-save be triggered internally on an explicit kill, but once the auto-save has been triggered by the internal timer (due to internal timer) and the modified note(s) have been auto-saved, an explicit kill IMO can be approximated with an application/system crash. The whole point of auto-saving notes is, IMHO, to prevent us from loosing information due to an abnormal termination of the program. Right?
So, in short, auto-save is working but PNotes fails to recover notes that have not been explicitly saved - at least once - before an abnormal termination of PNotes.
BTW, thanks for your prompt response.
Another auto-save related bug, IMO, is that after explicitly saving all notes ("Save All") and then crashing/killing PNotes, Pnotes on the next lauch displays a message "Program did not finish correctly last time[which is correct]. Would you like to load autosaved notes? Yes/No". This since there should be no auto-saved messages around to load at that time. Right?