From: Stefano Crocco <stefano.crocco@...>
Date: 2012-08-31T15:29:31+09:00
Subject: Re: Qt signals driving me crazy

On Friday 31 August 2012 Damjan Rems wrote
> Below is source of basic window with TreeWidget on left and TabWidget on
> the right. I stopped here because there is no way I can get
> itemActivated() signal to call my nitem_clicked method. I have tried
> practically everything I could find on net (there is very little Qt Ruby
> examples beyond basics). Current source shows the most complicated
> option, that I could have found ;-(
> 
> ruby 1.9.3
> qtbindings (4.6.3.4)
> kubuntu 10.4
> 
> 
> by
> TheR

The correct signature for the signal is 

'itemActivated( QTreeWidgetItem*, int )'

while you used

'itemActivated(TreeWidgetItem*, int )'

without the leading Q. You have the same problem in a couple of other places. 
Generally speaking, when you have problems with a signal-slot connection, one 
of the first things to do is to look at the output on standard error and see 
if you see a warning saying 'not such a signal' or 'not such a slot' (this 
warning is shown even if you're running ruby with warnings turned off, since 
it is generated from the Qt library on the C++ side. Unfortunately, it doesn't 
tell you where the wrong signal or slot name is).

I hope this helps

Stefano