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?
Further, in all *.ui files, should all occurrences of QString be changed to TQString?
Or, is there a build macro that is supposed to be changing those strings to TQString that is not functioning correctly?
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?
Darrell
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
Further, in all *.ui files, should all occurrences of QString be changed to TQString?
Yes.
A quick grep of the sources indicates a significant number of these corrections are needed. I'll start pecking at them.
To be sure I'm not making a mess, both of the following types of lines should be changed to TQString?
<signal>***(const QString&)</signal> <slot>***(const QString&)</slot>
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.
I tested tdebase by rebuilding with a patch and the xsession error disappeared. The patch did not resolve the What's This bug, but KControl functioned without incident.
Darrell
Further, in all *.ui files, should all occurrences of QString be
changed
to TQString?
Yes.
A quick grep of the sources indicates a significant number of these corrections are needed. I'll start pecking at them.
To be sure I'm not making a mess, both of the following types of lines should be changed to TQString?
<signal>***(const QString&)</signal> <slot>***(const QString&)</slot>
Yes, both should be changed. Any instance of a Q* object in a .ui file that is not part of a user-visible text string should be changed to its TQ* equivalent.
Tim
-
Darrell Anderson -
Timothy Pearson