trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] Q_LLONG vs. TQ_LLONG

From: Serghei Amelian <serghei@...>
Date: Fri, 30 Mar 2012 02:22:03 +0300
On Friday 30 March 2012 02:06:22 Darrell Anderson wrote:
> 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.

Check in .ui files too.


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




-- 
Serghei