Keep current document between sessions

[Robert Ancell]

Automatically save the scan information so simple-scan can be closed without losing any information

[Martin Pitt (pitti)]

"Automatically safe" -> to where? Into a "hidden" file in .cache/ so that it reappears when you open it again?

Shouldn't it rather follow the standard convention of just asking you when you try to close the app without having saved the current document?

[Michaël Van Dorpe (michael-vandorpe)]

I think this would be especially relevant in case simple-scan would crash. (I have not yet experienced any crashes, but I'm sure it's possible.) If you are scanning in batch, and not saving each and every scan separately prior to doing the next scan, you can lose a lot of scans in a crash.

[Martin Pitt (pitti)]

Michaël Van Dorpe [2009-12-21 16:11 -0000]:
> I think this would be especially relevant in case simple-scan would
> crash. (I have not yet experienced any crashes, but I'm sure it's
> possible.) If you are scanning in batch, and not saving each and every
> scan separately prior to doing the next scan, you can lose a lot of
> scans in a crash.

I agree, that would be handy. Perhaps it should store the staged
documents in ~/.cache/, and clean the cache after saving a document
or cleaning the "work area".

[Robert Ancell (robert-ancell)]

Absolutely they would be automatically saved in ~/.cache without asking (applications should never prompt the user about a detail like that). It also needs some sort of undo system in case you clear the document.

[papukaija (papukaija)]

This should be user configurable for privacy reasons.

[Michael Nagel (nailor)]

also see

load an initial pdf/tiff file and append pages
Simple Scan Bugs Bug #599065

Simple Scan crashes result in preventable data loss
Simple Scan Bugs Bug #897469