On Sat, May 24, 2008 at 1:43 PM, Phil Thompson <[EMAIL PROTECTED]> wrote:
>> To get back to the original problem, it seems I can't get any signal >> from QListView to work: clicked, doubleClicked, selectionChanged, you >> name it. I even tried connecting signals with qt designer, but those >> are not emitted either. > > So you need to post a small, complete example that's demonstrates the problem. In a rather embarrassing (and typical) twist of events, I managed to get the signals working while building my minimal example - obviously after rewriting my app to use listwidget. My app uses qscintilla, so I'll put back QListView back in there and see whether that causes problems. Or possibly I just botched the signal signature. Since you are implementing a new connection system, it would be pretty handy to be able to connect to signals just by name, foregoing signature altogether. Or, implement a "signal helper" function that gets a target object and signal name, and returns the full signature... -- Ville M. Vainio - vivainio.googlepages.com blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio' _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
