13 Sep
2012
13 Sep
'12
9:39 p.m.
Tim,
I noticed the following messages in my xsession log (GIT build):
TQObject::connect: No such signal KLineEdit::textChanged(const QString&)
TQObject::connect: (sender name: 'excludeLineedit')
TQObject::connect: (receiver name: 'SMServerConfigDlg')
Investigating revealed the errors always appear when I open KControl/TDE
Components/Session Manager. Further investigation revealed the likely
source is tdebase/kcontrol/smserver/smserverconfigdlg.ui:240:
<connection>
<sender>excludeLineedit</sender>
<signal>textChanged(const QString&)</signal> <--- problematic
string?
<receiver>SMServerConfigDlg</receiver>
<slot>configChanged()</slot>
</connection>
Should that line be TQString?
Yes.
Further, in all *.ui files, should all occurrences of
QString be changed
to TQString?
Yes.
Or, is there a build macro that is supposed to be
changing those strings
to TQString that is not functioning correctly?
No.
There are many occurences of QString in many *.ui
files in the full
source. If these all should be changed could this be the cause of various
bugs, such as What's This help tooltips no longer working in KControl?
It is possible, though there should be error messages in your .xsesson
errors file regarding invalid connections in the affected modules if this
is the case.
Tim