path: root/src
diff options
authorVolker Hilsheimer <>2019-08-21 10:05:33 +0200
committerVolker Hilsheimer <>2019-08-21 11:27:10 +0200
commitc4aa90cb566a58ce3e2a18de134b83d0a959fed2 (patch)
tree6a004d90130f61ae0021e7beeb98921b90e7bc77 /src
parent626340d45882c7dcb9e56e7bdbae38f04a5b1cd1 (diff)
Point out that dynamically modified meta objects are not threadsafe
Given that this is an exception, it doesn't invalidate the general thread-safety of static meta objects, and putting a locking mechanism into Qt for this would be complete over- (and performance-)kill. Task-number: QTBUG-70915 Change-Id: I4a538b977f5c2e8173cb236023e5d9ca34add5b5 Reviewed-by: Ulf Hermann <>
Diffstat (limited to 'src')
1 files changed, 7 insertions, 0 deletions
diff --git a/src/corelib/kernel/qmetaobject.cpp b/src/corelib/kernel/qmetaobject.cpp
index 666bb6eace..927d03f830 100644
--- a/src/corelib/kernel/qmetaobject.cpp
+++ b/src/corelib/kernel/qmetaobject.cpp
@@ -112,6 +112,13 @@ QT_BEGIN_NAMESPACE
are returned by classInfo(), and you can search for pairs with
+ \note Operations that use the meta object system are generally thread-
+ safe, as QMetaObjects are typically static read-only instances
+ generated at compile time. However, if meta objects are dynamically
+ modified by the application (for instance, when using QQmlPropertyMap),
+ then the application has to explicitly synchronize access to the
+ respective meta object.
\sa QMetaClassInfo, QMetaEnum, QMetaMethod, QMetaProperty, QMetaType,
{Meta-Object System}