Status of PyQt signals

General Discussion
1

Hi all,

I’ve been successfully usnig basic Signals from PyQt (Avo 1.0.1+Python
on Windows) but I’m ready to throw in the towel on using signals with
parameters:

I have a QTableWidget and am trying to catch the signal when someone
clicks on a cell:

QObject.connect(self.allpharmas,
                SIGNAL("currentCellChanged(int, int, int, int)"),
                self, SLOT("selectPharmacophore(int,int,int,int)"))

The signal never arrives at selectPharmacophore:
@pyqtSignature(“int,int,int,int”)
def selectPharmacophore(self, a, b, c, d):
self.debug(“select pharmacophore”)

Does anyone know whether I am doing something wrong here? If these
signals aren’t usable it really limits the possibilities of extending
Avo through Python.

  • Noel
2

Actually it seems to be working now :slight_smile: My only problem is that I
can’t figure out exactly why it was failing before…

  • Noel

On 17 November 2011 15:55, Noel O’Boyle baoilleach@gmail.com wrote:

Hi all,

I’ve been successfully usnig basic Signals from PyQt (Avo 1.0.1+Python
on Windows) but I’m ready to throw in the towel on using signals with
parameters:

I have a QTableWidget and am trying to catch the signal when someone
clicks on a cell:

QObject.connect(self.allpharmas,
SIGNAL(“currentCellChanged(int, int, int, int)”),
self, SLOT(“selectPharmacophore(int,int,int,int)”))

The signal never arrives at selectPharmacophore:
@pyqtSignature(“int,int,int,int”)
def selectPharmacophore(self, a, b, c, d):
self.debug(“select pharmacophore”)

Does anyone know whether I am doing something wrong here? If these
signals aren’t usable it really limits the possibilities of extending
Avo through Python.

  • Noel