* Qt 3.1 and xconfig
@ 2002-11-21 5:10 Nero
2002-11-22 15:09 ` Markus Plail
0 siblings, 1 reply; 2+ messages in thread
From: Nero @ 2002-11-21 5:10 UTC (permalink / raw)
To: linux-kernel
If you link against qt 3.1 (and this will be common soon, KDE 3.1
requires it), you can't change any of the options. There is a warning
when it is running:
QObject::connect: No such signal ConfigList::menuSelected(struct menu*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal ConfigList::menuSelected(struct menu*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Qt 3.1 and xconfig
2002-11-21 5:10 Qt 3.1 and xconfig Nero
@ 2002-11-22 15:09 ` Markus Plail
0 siblings, 0 replies; 2+ messages in thread
From: Markus Plail @ 2002-11-22 15:09 UTC (permalink / raw)
To: linux-kernel
* Nero writes:
>If you link against qt 3.1 (and this will be common soon, KDE 3.1
>requires it), you can't change any of the options. There is a warning
>when it is running:
>[error messages]
It works just fine here. QT 3.1.0.
regards
Markus
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-11-22 15:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-21 5:10 Qt 3.1 and xconfig Nero
2002-11-22 15:09 ` Markus Plail
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox