KDECore
#include <KAutoSaveFile>
Inherits QFile.
Public Member Functions | |
KAutoSaveFile (const KUrl &filename, QObject *parent=0) | |
KAutoSaveFile (QObject *parent=0) | |
~KAutoSaveFile () | |
KUrl | managedFile () const |
virtual bool | open (OpenMode openmode) |
virtual void | releaseLock () |
void | setManagedFile (const KUrl &filename) |
Static Public Member Functions | |
static QList< KAutoSaveFile * > | allStaleFiles (const QString &applicationName=QString()) |
static QList< KAutoSaveFile * > | staleFiles (const KUrl &filename, const QString &applicationName=QString()) |
Detailed Description
Creates and manages a temporary "auto-save" file.
Autosave files are temporary files that applications use to store the unsaved data in a file they have open for editing. KAutoSaveFile allows you to easily create and manage such files, as well as to recover the unsaved data left over by a crashed or otherwise gone process.
Each KAutoSaveFile object is associated with one specific file that the application holds open. KAutoSaveFile is also a QObject, so it can be reparented to the actual opened file object, so as to manage the lifetime of the temporary file.
Typical use consists of:
- verifying whether stale autosave files exist for the opened file
- deciding whether to recover the old, autosaved data
- if not recovering, creating a KAutoSaveFile object for the opened file
- during normal execution of the program, periodically save unsaved data into the KAutoSaveFile file.
KAutoSaveFile holds a lock on the autosave file, so it's safe to delete the file and recreate it later. Because of that, disposing of stale autosave files should be done with releaseLock(). No lock is held on the managed file.
Examples: Opening a new file:
The function recoverFiles could loop over the list of files and do this:
If the file is unsaved, periodically write the contents to the save file:
When the user saves the file, the autosaved file is no longer necessary and can be removed or emptied.
Definition at line 129 of file kautosavefile.h.
Constructor & Destructor Documentation
Constructs a KAutoSaveFile for file filename
.
The temporary file is not opened or created until actually needed. The file filename
does not have to exist for KAutoSaveFile to be constructed (if it exists, it will not be touched).
- Parameters
-
filename the filename that this KAutoSaveFile refers to parent the parent object
Definition at line 71 of file kautosavefile.cpp.
|
explicit |
This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts. Constructs a KAutoSaveFile object.
Note that you need to call setManagedFile() before calling open().
- Parameters
-
parent the parent object
Definition at line 79 of file kautosavefile.cpp.
KAutoSaveFile::~KAutoSaveFile | ( | ) |
Destroys the KAutoSaveFile object, removes the autosave file and drops the lock being held (if any).
Definition at line 86 of file kautosavefile.cpp.
Member Function Documentation
|
static |
Returns all stale autosave files left behind by crashed or otherwise gone instances of this application.
If not given, the application name is obtained from QCoreApplication, so be sure to have set it correctly before calling this function.
See staleFiles() for information on the returned objects.
Definition at line 190 of file kautosavefile.cpp.
KUrl KAutoSaveFile::managedFile | ( | ) | const |
Retrieves the URL of the file managed by KAutoSaveFile.
This is the same URL that was given to setManagedFile() or the KAutoSaveFile constructor.
This is the name of the real file being edited by the application. To get the name of the temporary file where data can be saved, use fileName() (after you have called open()).
Definition at line 92 of file kautosavefile.cpp.
|
virtual |
Opens the autosave file and locks it if it wasn't already locked.
The name of the temporary file where data can be saved to will be set by this function and can be retrieved with fileName(). It will not change unless releaseLock() is called. No other application will attempt to edit such a file either while the lock is held.
- Parameters
-
openmode the mode that should be used to open the file, probably QIODevice::ReadWrite
- Returns
- true if the file could be opened (= locked and created), false if the operation failed
Definition at line 115 of file kautosavefile.cpp.
|
virtual |
Closes the autosave file resource and removes the lock file.
The file name returned by fileName() will no longer be protected and can be overwritten by another application at any time. To obtain a new lock, call open() again.
This function calls remove(), so the autosave temporary file will be removed too.
Definition at line 105 of file kautosavefile.cpp.
void KAutoSaveFile::setManagedFile | ( | const KUrl & | filename | ) |
Sets the URL of the file managed by KAutoSaveFile.
This should be the name of the real file being edited by the application. If the file was previously set, this function calls releaseLock().
- Parameters
-
filename the filename that this KAutoSaveFile refers to
Definition at line 97 of file kautosavefile.cpp.
|
static |
Checks for stale autosave files for filename
.
Returns a list of autosave files that contain autosaved data left behind by other instances of the application, due to crashing or otherwise uncleanly exiting.
It is the application's job to determine what to do with such unsaved data. Generally, this is done by asking the user if he wants to see the recovered data, and then allowing the user to save if he wants to.
If not given, the application name is obtained from QCoreApplication, so be sure to have set it correctly before calling this function.
This function returns a list of unopened KAutoSaveFile objects. By calling open() on them, the application will steal the lock. Subsequent releaseLock() or deleting of the object will then erase the stale autosave file.
Definition at line 151 of file kautosavefile.cpp.
The documentation for this class was generated from the following files:
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 22:47:10 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.