| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Task-number: QTBUG-8729
|
|
|
|
|
|
|
|
|
|
| |
delivered queued.
Since we emit the signal while the locks are in place, we have to have
queued delivery.
Task-number: QT-760
Reviewed-by: Trust Me
|
| |
|
|
|
|
| |
Issue found while debugging KDE applications.
|
|
|
|
|
| |
Merge-request: 442
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
|
|
|
|
|
|
| |
avoid needless atomic operations
Merge-request: 442
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
|
|
|
|
|
|
|
| |
We must wait for a reply in case the reply hasn't been received yet,
not if it has already been received. Simple typo.
Task-number: QT-2307
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
| |
Task-number: QTBUG-5979
Reviewed-By: TrustMe
|
|
|
|
|
| |
Task-number: QTBUG-5979
Reviewed-By: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of simply counting how many times we're watching a service,
also map a service to its owner. This allows us to provide a faster,
cached GetNameOwner too.
Technically, this could mean that a service that is started in-between
event loops could remain invalid for a longer period of time. I'm not
sure this is an issue -- will need some testing in KDE.
Task-number: QTBUG-5979
Reviewed-By: TrustMe
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
C++ booleans are 1 byte in size, but D-Bus booleans (dbus_bool_t) are
4 bytes. That means a boolean with a zero in the LSB byte but non-zero
garbage in the high bytes is a valid "false" in C++, but libdbus-1
will turn that to true when sending.
Task-number: QTBUG-7041
Reviewed-By: Trust Me
BT: yes
|
|\ \
| |/
| |
| |
| | |
Conflicts:
mkspecs/macx-g++40/qplatformdefs.h
|
| |
| |
| |
| |
| |
| |
| |
| | |
If we made calls on a QDBusConnection that isn't connected, the d
pointer is 0. Ensure we don't crash.
Task-number: QTBUG-6571
Reviewed-by: Bradley T. Hughes
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The reason is that the private headers don't exist in any of the -I
lines, so they need to be found by the preprocessor relative to the
source file, which means "".
Task-number: QTBUG-6665
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| | |
We trust the bus, so no need to match per path. The sender and the
interface should be enough for us.
|
| |
| |
| |
| |
| | |
Add the note that this signal will cause many activations and that
QDBusServiceWatcher is better.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, we were relying on NameOwnerChanged to notify us of our
own names. This worked because we got all NameOwnerChanged that
happened on the bus.
Now, we only get those we're interested in. Instead of watching for
newOwner==baseService, let's just use the NameAcquired and NameLost
signals, that the D-Bus server sends to us anyway.
Task-number: QTBUG-5979
|
| |
| |
| |
| |
| |
| | |
now"
This reverts commit f01c631f84f9373b06d0572bfed7a4e8213a46a7.
|
| |
| |
| |
| |
| |
| |
| |
| | |
QtDBus itself""
This reverts commit db1cff73726ff12d50139769dc8071f9e9173261.
Task-number: QTBUG-5979
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Over src/ tools/ examples/ and demos/
|
| | | |
|
| | |
| | |
| | |
| | | |
Task-number: QTBUG-5972
|
|/ /
| |
| |
| |
| |
| | |
This partially reverts commit 1176ecf0b533279e5a1c97f183e5c5f1c57fb188.
Task-number: QTBUG-5972
|
|\ \ |
|
| |\ \ |
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: Trust Me
|
| | |\ \ \
| | | |/ / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When exporting an object to DBus, and the object has N signals, this code
was connecting the QDBusConnectionPrivate multiple times to the destroyed
signal of the object.
Merge-request: 1961
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| | |/ /
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the introspection failed, we won't have a meta object, meaning you
cannot connect to signals or invoke methods via the slot
mechanism. But you can still make calls.
The isValid() functionality is preserved because there is no owner for
this object.
Reviewed-By: Harald Fernengel
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Signals are badly mishandled in QtDBus. In the spec, they are "in"
arguments, but we generate "Out" annotations for them. What's worse,
we were using the wrong count.
QTBUG-914 is about fixing the directionality. While that task isn't
fixed, at least use the right count.
Task-number: QTBUG-5563
Reviewed-by: TrustMe
|
|/ / / |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
We want people to not use this signal directly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We were using this signal to update the signal hooks when the remote
service changed. That meant each Qt app received every single service
creation, change or destruction.
Now we only watch the services we're really interested in.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QDBusConnectionPrivate
I'll need to recurse into the signal connection mechanism in the next
commit.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use null services to indicate we're not interested in the owner, but
empty-but-not-null to indicate we don't know what the owner is. Since
empty service names are not valid, this will mean that this rule won't
match.
|
| | |
| | |
| | |
| | |
| | | |
This allows us to listen only to the activations we're really
interested in.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
matching.
The bus allows us to match string arguments when receiving messages.
This is very useful for the NameOwnerChanged signal, whose first
argument is usually what we're interested in.
By using these new functions, you can restrict receiving of signals to
those that you truly want, instead of receiving NameOwnerChanged for all
services registered/unregistered on the bus.
|
|/ /
| |
| |
| | |
I'll use this feature to match the NameOwnerChanged signal from the bus.
|
| |
| |
| |
| | |
Reviewed-by: Markus Goetz
|
| |
| |
| |
| |
| |
| | |
The minimum version for the recursive mutexes is D-Bus 0.93. That's
also the same version that introduced the default thread functions. So
we don't need to provide ours anymore, just use the default.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
At least in D-Bus 1.2.16, there's a deadlock caused by locking an
already-locked mutex. When Qt is linked to libdbus-1 instead of
dynamically loading it, it maintains legacy compatibility by only
providing the non-recursive mutexes, which triggers this deadlock.
The recursive functions have been present since 0.93, so I guess the
non-recursive variants aren't tested.
Report: https://bugzilla.novell.com/show_bug.cgi?id=482749#c30
|