#2662 closed enhancement (fixed)
Auto-save
Reported by: | anonymous | Owned by: | jttt |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | autosave, auto-save, exception | Cc: | luttermann@…, Michi, richlv, skyper |
Description
Seems that this app is really good at catching exepctions, it would be practical to have it auto-save to a temporary file if it does so. So that no data would be lost.
Attachments (0)
Change History (13)
comment:1 by , 15 years ago
Summary: | Auto-safe → Auto-save |
---|
comment:2 by , 15 years ago
Cc: | added |
---|
follow-up: 6 comment:5 by , 15 years ago
Now when OsmPrimitive has reference to the Dataset are two ways of implementing such functionality possible - one is saving complete dataset every few minutes, another option is logging all changes done on primitives. That would allow to replay all changes after crash
comment:6 by , 15 years ago
Replying to jttt:
- one is saving complete dataset every few minutes,
... in which case we would probably need some mechanism for "locking" a dataset. Timed auto-saving will probably run on its own thread and with respect to the dataset it should have transactional properties. During autosave it should not be possible to modify the dataset itself (adding/removing a primitive), nor one of its primitives (move a primitive, add a primitive, etc.).
comment:7 by , 15 years ago
Keywords: | autosave auto-save added; autosafe auto-safe removed |
---|
I support this enhancement request. I just lost 1 houre of data after JOSM crashed. Why can't the datalayer(s) be saved every x seconds into a file. This will minimize the lost of new data in case of a crash.
comment:8 by , 15 years ago
Cc: | added |
---|
comment:10 by , 14 years ago
Cc: | added |
---|
comment:11 by , 14 years ago
Owner: | changed from | to
---|
comment:12 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:13 by , 14 years ago
Basic implementation of autosave, no gui - only configurable using Einstein preferences. By default on, should save all osm layers every 5 minutes. When josm is restarted after crash, unsaved layers should be restored.
Property autosave.filesPerLayer - number of files kept for one layer. By default 1 can be set to higher number to get snapshots of layer every autosave interval.
I like this idea. I find myself uploading more often than I would like, so as to avoid data loss if JOSM crashes. An auto-save function would avoid this. Also, what is the meaning of "Save" in JOSM? The wiki just says "Save the currently active layer", when what I really want to do is save my changes - is this actually the same thing?