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

I'll grep and peck a little more. Just like working in the blind after a display terminal crash. I think this is going to be some QString issue buried way down in some base struct or class that gets inherited all through the knetworkmanager code. I've grepped until I'm blue -- do you know how many results you get for QString :)

I wish Tim had time to post a basic "TQ" troubleshooting strategy. Probably could save everybody time. :)

Darrell