PluginManager::getObject(): Remove special support for aggregates

Since no one is using it and it's faster this way.

Change-Id: Ib60d3a54aed98011b2fb4bb7d159e219abebfa7e
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
This commit is contained in:
Daniel Teske
2014-05-06 17:56:30 +02:00
parent 01d9e4d70b
commit cf8cae595c
2 changed files with 8 additions and 16 deletions

View File

@@ -108,9 +108,7 @@ enum { debugLeaks = 0 };
Plugins (and everybody else) can add objects to a common 'pool' that is located in
the plugin manager. Objects in the pool must derive from QObject, there are no other
prerequisites. All objects of a specified type can be retrieved from the object pool
via the getObjects() and getObject() functions. They are aware of Aggregation::Aggregate, i.e.
these functions use the Aggregation::query functions instead of a qobject_cast to determine
the matching objects.
via the getObjects() and getObject() functions.
Whenever the state of the object pool changes a corresponding signal is emitted by the plugin manager.
@@ -220,9 +218,7 @@ enum { debugLeaks = 0 };
Retrieves the object of a given type from the object pool.
This function is aware of Aggregation::Aggregate. That is, it uses
the \c Aggregation::query functions instead of \c qobject_cast to
determine the type of an object.
This function uses \c qobject_cast to determine the type of an object.
If there are more than one object of the given type in
the object pool, this function will choose an arbitrary one of them.
@@ -234,9 +230,7 @@ enum { debugLeaks = 0 };
Retrieves all objects of a given type from the object pool.
This function is aware of Aggregation::Aggregate. That is, it uses
the \c Aggregation::query functions instead of \c qobject_cast to
determine the type of an object.
This function uses \c qobject_cast to determine the type of an object.
\sa addObject()
*/