[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] PyKDE: Can't connect to signal
From:       "Phil Thompson" <phil () riverbankcomputing ! co ! uk>
Date:       2004-10-27 9:18:04
Message-ID: 55946.82.68.80.137.1098868684.squirrel () 82 ! 68 ! 80 ! 137
[Download RAW message or body]

> Hello,
>
> First of all, this should not be a problem with WIds because I am
> connecting to signals like activeWindowChanged(WId) without problems.
>
> With PyKDE 3.11.3 (hand compiled) and kde 3.2.3 from Mandrake 10.1, I am
> trying to connect to the signal
>
>   void KWinModule::windowChanged ( WId id, const unsigned long *
> properties)
>
> or at least the deprecated
>
>   void KWinModule::windowChanged (WId id, unsigned int properties)
>
> I have tried to connect with
>
>  SIGNAL("windowChanged(WId, unsigned long)")
>
>  SIGNAL("windowChanged(WId, const unsigned long*)")
>
>  SIGNAL("windowChanged(WId, unsigned int)")
>
> with no success (RuntimeError: Signal has wrong argument types for slot)
>
>
> What's happening? Thanks for any help,

It's a SIP "feature". In signal arguments SIP deals with the underlying
data type (ie. whatever WId is typedef'd from), but Qt deals with WId
itself. So, between them, they can't agree. This will be fixed in the next
release of SIP.

Phil

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]