Re: [trinity-devel] Q_LLONG vs. TQ_LLONG

I'm debugging various problems with digikam. When I start digikam from the terminal I see the following: TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageTagsChanged(Q_LLONG) TQObject::connect: (sender name: 'unnamed') TQObject::connect: (receiver name: 'unnamed') TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageRatingChanged(Q_LLONG) TQObject::connect: (sender name: 'unnamed') TQObject::connect: (receiver name: 'unnamed') TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageDateChanged(Q_LLONG) TQObject::connect: (sender name: 'unnamed') TQObject::connect: (receiver name: 'unnamed') TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageCaptionChanged(Q_LLONG) TQObject::connect: (sender name: 'unnamed') TQObject::connect: (receiver name: 'unnamed') The strings repeat a second time. Looking at the sources I see TQ_LLONG but not Q_LONG.

TQ_LLONG is defined in tqt.h. What is causing these messages? Darrell