AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

QDBusInterface: mention QtDBus caching in documentation

Browse Source 
QtDBus caches well known interface objects when there is a non-emtpy
interface name passed to the QDBusInterface constructor.

This commit amends the constructor documentation to explain this
behavior.

Change-Id: Ic51836be6d833411500ea05fcc895cd4f6e96407
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
This commit is contained in:
Elvis Angelaccio 2019-11-24 21:11:25 +01:00
parent 4e9e9c2c17
commit c0fb2a8173
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/dbus/qdbusinterface.cpp
View File

@ -204,7 +204,9 @@ QDBusInterfacePrivate::~QDBusInterfacePrivate()
interface \a interface on object at path \a path on service \a
service, using the given \a connection. If \a interface is an
empty string, the object created will refer to the merging of all
interfaces found in that object.
interfaces found by introspecting that object. Otherwise if
\a interface is not empty, the QDBusInterface object will be cached
to speedup further creations of the same interface.
\a parent is passed to the base class constructor.