KDE/kdevplatform

Andreas Pakulat apaku at gmx.de
Wed Apr 8 15:04:24 UTC 2009


On 05.04.09 20:22:25, Andreas Pakulat wrote:
> On 05.04.09 19:31:23, David Nolden wrote:
> > Am Sonntag 05 April 2009 16:06:48 schrieb Andreas Pakulat:
> > > Hmm, indeed there seems to be no documentation about this (except the
> > > soure code). However at least for QAction::triggered() this is used in
> > > all examples in Qt itself, so IMHO its pretty safe to assume this is
> > > officially supported.
> > >
> > > If you want to I'll create a bugreport with QtSoftware about the missing
> > > docs.
> > 
> > Feel free to do it. Since it's undocumented, the big question is whether it's 
> > safe to generally assume that default-parameters in signals can be left out of 
> > the specification. I haven't checked th Qt source code, but I don't believe 
> > that it works like that, since Qt uses string-matching internally for the 
> > signals/slots, and this would mean quite a bit more complexity.
> 
> I did have a quick look at the sources, but the connect code is quite
> hard to understand without some in-depth knowledge about the moc-system.
> 
> BTW: the same thing doesn't work in Qt3, so I think its safe to assume
> that this is actually something they did on purpose. Will ask them
> tomorrow for clarification.

FWIW: 
http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry&id=250687

So it seems this is a proper feature.

Andreas
 
-- 
You should emulate your heros, but don't carry it too far.  Especially
if they are dead.




More information about the KDevelop-devel mailing list