Thiago Macieira d2a98df9bc Make sure that signal disconnects don't disconnect too much ... There has been a latent bug forever in QtDBus that would make a signal disconnect actually disconnect too much. The reason is that disconnectNotify() is called every time a signal is disconnected from a receiver, but that doesn't mean it was the last connection. This test checks whether disconnecting from voidSignal() to our test receiver will also disconnect from exitLoop(). If it does, we'll get a timeout. I could have implemented it with two receivers, but in the buggy case, it would always fail first in the timeout verification. Change-Id: I5766d8a38594eb25e65b304913251303660fad41 Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>		2013-03-19 07:03:17 +01:00
..
qpinger	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
test	Set the Qt API level to compatibility mode in all tests.	2012-08-01 15:37:46 +02:00
interface.cpp	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
interface.h	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
org.qtproject.QtDBus.Pinger.xml	Finish cleaning up com.trolltech -> org.qtproject in QtDBus	2012-04-16 00:07:39 +02:00
pinger.cpp	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
pinger.h	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
qdbusabstractinterface.pro	Finish cleaning up com.trolltech -> org.qtproject in QtDBus	2012-04-16 00:07:39 +02:00
tst_qdbusabstractinterface.cpp	Make sure that signal disconnects don't disconnect too much	2013-03-19 07:03:17 +01:00