View Revisions: Issue #1970
[ All Revisions ] [ Back to Issue ]
| Summary | 0001970: full-save datestamps | ||
|---|---|---|---|
| Revision | 2013-12-23 14:00 by Vincent Sanders | ||
| Description | Problem: A full-save application does not contain a !runimage so that, if the full-save is copied, the datestamp of the original full-save is lost. To determine when it was saved it is then necessary to open the full-save application and inspect the datestamp of the 'index' file. Some months ago, this problem caused several hundred of my full-saves to be re-stamped with the date of installation of a new hard-drive. Suggestion: A full-save application should contain a !runimage, so that its datestamp will determine the datestamp of the full-save application. The !runimage could most usefully be a URL file, containing the URL of the page. See too my feature request 'full-save should also save the page url' at http://sourceforge.net/tracker/index.php?func=detail&aid=1365047&group_id=51719&atid=464315 Tony |
||
| Revision | 2006-11-10 18:42 by Tony Moore | ||
| Description | Problem: A full-save application does not contain a !runimage so that, if the full-save is copied, the datestamp of the original full-save is lost. To determine when it was saved it is then necessary to open the full-save application and inspect the datestamp of the 'index' file. Some months ago, this problem caused several hundred of my full-saves to be re-stamped with the date of installation of a new hard-drive. Suggestion: A full-save application should contain a !runimage, so that its datestamp will determine the datestamp of the full-save application. The !runimage could most usefully be a URL file, containing the URL of the page. See too my feature request 'full-save should also save the page url' at http://sourceforge.net/tracker/index.php?func=detail&aid=1365047&group_id=51719&atid=464315 Tony |
||