Re: [trinity-devel] knetworkmanager8 - patched QCString -> TQCString bug, now get TQCString error in SlotActivate()

The next error encountered after the patch was: [ 75%] Building CXX object knetworkmanager-0.8/src/CMakeFiles/tdeinit_knetworkmanager-shared.dir/knetworkmanager-menuitem.cpp.o cd /build/src/build/knetworkmanager-0.8/src && /usr/bin/c++ -Dtdeinit_knetworkmanager_shared_EXPORTS -DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC -I/build/src/build/knetworkmanager-0.8/src -I/build/src/build -I/opt/trinity/include -I/opt/tqt3/include -I/usr/include/tqt -I/opt/trinity/include/dbus-1-tqt -I/usr/include/NetworkManager -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -UQT_NO_ASCII_CAST -o CMakeFiles/tdeinit_knetworkmanager-shared.dir/knetworkmanager-menuitem.cpp.o -c /build/src/knetworkmanager8/knetworkmanager-0.8/src/knetworkmanager-menuitem.cpp /build/src/knetworkmanager8/knetworkmanager-0.8/src/knetworkmanager-menuitem.cpp: In member function 'void NetworkMenuItem::slotActivate()': /build/src/knetworkmanager8/knetworkmanager-0.8/src/knetworkmanager-menuitem.cpp:99:163: error: 'QCString' was not declared in this scope make[2]: *** [knetworkmanager-0.8/src/CMakeFiles/tdeinit_knetworkmanager-shared.dir/knetworkmanager-menuitem.cpp.o] Error 1 make[2]: Leaving directory `/build/src/build' make[1]: *** [knetworkmanager-0.8/src/CMakeFiles/tdeinit_knetworkmanager-shared.dir/all] Error 2 make[1]: Leaving directory `/build/src/build' make: *** [all] Error 2 I attempted to patch the TQString -> TQCString consistent with the earlier patch -- but that obviously failed. I have grepped QCString and TQString looking at the declarations, but I am over my c++ multi-inheritance limit at this point. Can someone point me in the right direction to correct the QCString error. Admittedly, my first attempt may have caused the second error, so can someone confirm the first patch as well. Thanks.