[Qt-creator] SIGNAL-completion in qtcreator-1.3.80 for QState
Lindeijer Thorbjorn (Nokia-D-Qt/Berlin)
thorbjorn.lindeijer at nokia.com
Wed Jan 6 15:32:50 CET 2010
On 12/21/2009 01:49 PM, ext Wilhelm Meier wrote:
> Hi,
>
> if I try to use the code-completion for the signal entered(), e.g.
>
> QObject::connect(off, SIGNAL(entered()), a, SLOT(foo()));
>
> the qtcreator doesn't list the entered() signal for completion. Other
> signals (e.g. finished()) are listed.
>
> What's wrong here?
This is because of a workaround used in qabstractstate.h, which goes
like this:
Q_SIGNALS:
#if !defined(Q_MOC_RUN) && !defined(qdoc)
private: // can only be emitted by QAbstractState
#endif
void entered();
void exited();
It makes moc and qdoc see 'entered' and 'exited' as signals, while the
compiler (and Qt Creator) will see them as private methods.
This is probably quite tricky to work around, since we can't generally
have Qt Creator pretend to be moc or qdoc when parsing the code.
Regards,
Bjørn
--
Thorbjørn Lindeijer
Software Engineer
Nokia, Qt Development Frameworks
More information about the Qt-creator-old
mailing list