summaryrefslogtreecommitdiffstats
path: root/src/corelib
diff options
context:
space:
mode:
authorVolker Hilsheimer <volker.hilsheimer@qt.io>2021-04-12 14:05:12 +0200
committerVolker Hilsheimer <volker.hilsheimer@qt.io>2021-04-13 10:48:50 +0200
commitae3d4b8f6b42da8c38f5146527bd18cab5bb5a95 (patch)
treefe45ed81aa33512309c09c2cba621d10acad9a2a /src/corelib
parentf6651d54df51ca65d9e4398512cc7f92b1e8f007 (diff)
Fix qdoc warnings from new QLockFile members
Change-Id: I06210fe37a3d90a958064fff48331a34bced2a8b Reviewed-by: Paul Wicking <paul.wicking@qt.io> Reviewed-by: Nico Vertriest <nico.vertriest@qt.io>
Diffstat (limited to 'src/corelib')
-rw-r--r--src/corelib/io/qlockfile.cpp7
1 files changed, 3 insertions, 4 deletions
diff --git a/src/corelib/io/qlockfile.cpp b/src/corelib/io/qlockfile.cpp
index 9dc0102574..032be3b7a1 100644
--- a/src/corelib/io/qlockfile.cpp
+++ b/src/corelib/io/qlockfile.cpp
@@ -184,14 +184,13 @@ void QLockFile::setStaleLockTime(int staleLockTime)
\overload
\since 6.2
- Sets \a staleLockTime to be an interval after which a lock file is considered
- stale.
+ Sets the interval after which a lock file is considered stale to \a value.
The default value is 30 seconds.
If your application typically keeps the file locked for more than 30 seconds
(for instance while saving megabytes of data for 2 minutes), you should set
a bigger value using setStaleLockTime().
- The value of \a staleLockTime is used by lock() and tryLock() in order
+ The value of staleLockTime() is used by lock() and tryLock() in order
to determine when an existing lock file is considered stale, i.e. left over
by a crashed process. This is useful for the case where the PID got reused
meanwhile, so one way to detect a stale lock file is by the fact that
@@ -212,7 +211,7 @@ int QLockFile::staleLockTime() const
return d->staleLockTime;
}
-/*! \fn std::chrono::milliseconds staleLockTimeAsDuration() const
+/*! \fn std::chrono::milliseconds QLockFile::staleLockTimeAsDuration() const
\overload
\since 6.2