Here we go again [ was: Re: [PyKDE] Help -- QObject.connect() fails -- WId not recognized. ]

[Maurizio Colucci]

Jim Bublitz wrote:

>On Wednesday 25 August 2004 02:22, Maurizio Colucci wrote:
>
>  
>
>>It works! You are the hell of a hacker :-)
>>    
>>
>
>  
>
>>Now, I can't ask my users to compile pykde, so I suppose...?
>>    
>>
>
>I can add the changes transparently to PyKDE - it's always done some 
>post-processing of sip code for odd cases like this (although much less in 
>recent releases). It's just a little tedious to cover all the possible build 
>combinations now, so I appreciate knowing that it works before diving in. It 
>doesn't really require any maintenance once I get it working. All of the 
>KWinModule signals should work.
>
>I should have a new release later this week/early next week with one or two 
>other bug fixes.
>
>
>  
>
Hello everybody,

I notice the problem with WId still stands:

QObject.connect(kwin_module
                , SIGNAL("activeWindowChanged(int)"), 
on_active_window_changed)

causes the usual error:

 File "./one-finger.py", line 1763, in ?
    , SIGNAL("activeWindowChanged(WId)"), on_active_window_changed)
RuntimeError: Signal has wrong argument types for slot

I am using the suse 9.1 packages on suse 9.1, kde 3.2 official.

-rw-r--r--  1 root root 5656175 Sep 22 22:07 PyKDE-3.11.1-1.i586.rpm
-rw-r--r--  1 root root 2300326 Sep 22 22:18 PyQt-3.12-1.i586.rpm
-rw-r--r--  1 root root  762164 Sep 22 22:19 qscintilla-1.60-1.3_1.i586.rpm
-rw-r--r--  1 root root  198520 Sep 22 22:15 sip-4.0-1.i586.rpm

It was my understanding the problem was fixed in the latest release. 
What happened?

Cheers
Mau