|
|
@ -105,11 +105,11 @@
|
|
|
|
* this is because usually get called by the class which they belong to,
|
|
|
|
* this is because usually get called by the class which they belong to,
|
|
|
|
* and one'd assume that a class author doesn't use deprecated methods of his
|
|
|
|
* and one'd assume that a class author doesn't use deprecated methods of his
|
|
|
|
* own class. The only exception to this are signals which are connected to
|
|
|
|
* own class. The only exception to this are signals which are connected to
|
|
|
|
* other signals; they get invoked from tqmoc-generated code. In any case,
|
|
|
|
* other signals; they get invoked from moc-generated code. In any case,
|
|
|
|
* printing a warning message in either case is not useful.
|
|
|
|
* printing a warning message in either case is not useful.
|
|
|
|
* For slots, it can make sense (since slots can be invoked directly) but be
|
|
|
|
* For slots, it can make sense (since slots can be invoked directly) but be
|
|
|
|
* aware that if the slots get triggered by a signal, the will get called from
|
|
|
|
* aware that if the slots get triggered by a signal, the will get called from
|
|
|
|
* tqmoc code as well and thus the warnings are useless.
|
|
|
|
* moc code as well and thus the warnings are useless.
|
|
|
|
*
|
|
|
|
*
|
|
|
|
* \par
|
|
|
|
* \par
|
|
|
|
* Also note that it is not possible to use KDE_DEPRECATED for classes which
|
|
|
|
* Also note that it is not possible to use KDE_DEPRECATED for classes which
|
|
|
|