Qt 3.1 and xconfig
For some reason this didn't get to the list last time I sent it, so here it is again:
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')
Hi,
Quoted 10 lines · Nero
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 signalConfigList::menuSelected(struct menu*)QObject::connect: (sender name: 'unnamed')QObject::connect: (receiver name: 'unnamed')QObject::connect: No such signalConfigList::menuSelected(struct menu*)QObject::connect: (sender name: 'unnamed')QObject::connect: (receiver name: 'unnamed')
This is a bug in QT, moc filters the 'struct' keyword from signal specification, but connect call doesn't do this. I can work around this, but could you please report this also to trolltech?
bye, Roman