© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
A partial workaround, as others have mentioned, might be to check the temporary file's timestamp. Compare it with the known timestamp that the file had, when it was originally downloaded.
If they are different, then assume the user has edited the file or otherwise taken action to cause it to be different from what it was when it was originally downloaded. Then, offer the chance for the user to save the file to a real location, going through the usual Save As dialog, and DO NOT DELETE the temporary file automatically!
Hopefully, that will be enough to protect users from the common mistake of editing temporary files, then having them automatically cleaned up, thus losing all of their edits....