From b256c47d625c519a88fe9dd96611015445776434 Mon Sep 17 00:00:00 2001 From: David Faure Date: Mon, 19 Nov 2012 14:10:33 +0100 Subject: Document what the QMimeDatabase constructor really does. Change-Id: I8d4dcc92296163dea7b78fbb0ceefaee08e57a94 Reviewed-by: Simon Hausmann Reviewed-by: Allan Sandfeld Jensen --- src/corelib/mimetypes/qmimedatabase.cpp | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'src/corelib/mimetypes') diff --git a/src/corelib/mimetypes/qmimedatabase.cpp b/src/corelib/mimetypes/qmimedatabase.cpp index c141eb9eb4..5acc290475 100644 --- a/src/corelib/mimetypes/qmimedatabase.cpp +++ b/src/corelib/mimetypes/qmimedatabase.cpp @@ -289,7 +289,12 @@ bool QMimeDatabasePrivate::inherits(const QString &mime, const QString &parent) /*! \fn QMimeDatabase::QMimeDatabase(); - Constructs this QMimeDatabase object. + Constructs a QMimeDatabase object. + + It is perfectly OK to create an instance of QMimeDatabase every time you need to + perform a lookup. + The parsing of mimetypes is done on demand (when shared-mime-info is installed) + or when the very first instance is constructed (when parsing XML files directly). */ QMimeDatabase::QMimeDatabase() : d(staticQMimeDatabase()) -- cgit v1.2.3