Stephen Kelly 0efa445141 Create a way to inform moc about private signals. ... Moc checks for the use of the QPrivateSignal struct, which is part of the Q_OBJECT macro and is private to each class that uses it. Moc then generates a name of the signal which does not include the private struct, and generates code to invoke such signals with an instance of the private struct. This way we can mark private signals as such and prevent them from being emitted from subclasses or from outside of the class entirely. The drawback to this is that it only works if the private signal has no default arguments. However, at least in Qt, there are no such signals. Change-Id: Id16eadaa8d3c36a2c3b265077877f3e1d8304c84 Reviewed-by: Olivier Goffart <ogoffart@woboq.com>		2012-07-13 01:51:42 +02:00
..
moc	Create a way to inform moc about private signals.	2012-07-13 01:51:42 +02:00
qdbuscpp2xml	Change remaining uses of {to,from}Ascii to {to,from}Latin1 [QtDBus]	2012-05-07 05:05:30 +02:00
qdbusxml2cpp	Add unit testing for the qdbusxml2cpp tool	2012-04-21 01:18:56 +02:00
qmake	test behavior of $${absolute,relative}_path() with empty 1st argument	2012-07-12 17:19:09 +02:00
rcc	Replace QTEST_APPLESS_MAIN with QTEST_MAIN in tests using QProcess	2012-06-05 06:12:20 +02:00
uic	Replace QTEST_APPLESS_MAIN with QTEST_MAIN in tests using QProcess	2012-06-05 06:12:20 +02:00
tools.pro	Add unit testing for the qdbusxml2cpp tool	2012-04-21 01:18:56 +02:00