Re: [PyQt] [SOLVED] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Kah Fai Chong
Thanks Brian. It is working fine now! Thanks everyone on this. Thanks Kah Fai From: Brian Kelley [mailto:kel...@eyesopen.com] Sent: Friday, April 27, 2012 2:08 AM To: Kah Fai Chong; 'pyqt@riverbankcomputing.com' Subject: Re: [SOLVED] [PyQt] sip: __or__() unsupported function return type - pr

[PyQt] Always show a QLineEdit as QItemDelegate

2012-04-26 Thread Jake Richards
Hello: I've got a QTreeView that uses a QLineEdit as a QItemDelegate for one of it's columns. The problem is that I want to display the QLineEdit all the time, not just when the user double clicks and starts editing. Am I using the wrong approach to accomplish this? I was using a QTreeWidget w

Re: [PyQt] QTreeView DragDropMode (Code attached)

2012-04-26 Thread hosscomp
This is a zip file of the Exlipse project if anyone cares to take a look. At this point I am trying to figure out why the dragEnterEvent in compassTreeView.py doesn't cause a move action when source is self. http://python.6.n6.nabble.com/file/n4931964/CompassGui.zip CompassGui.zip -- View this m

Re: [PyQt] [SOLVED] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Daniel Barbeau
Oh nice to see you managed to hunt down this bug! Will test this in a few days! Thanks! Daniel - Mail original - > De: "Brian Kelley" > À: "Kah Fai Chong" , "pyqt@riverbankcomputing.com" > > Envoyé: Jeudi 26 Avril 2012 20:08:17 > Objet: Re: [PyQt] [SOLVED] sip: __or__() unsupported funct

Re: [PyQt] Cannot 'configure' PyQt4.9 before build on Linuxmint

2012-04-26 Thread Hans-Peter Jansen
Am Wednesday 25 April 2012 14:28:54 schrieb Brian Kelley: > That would have been nice, except (1) This affected multiple distress that > did not have the openSUSE build service (2) I need to build with multiple > pythons (2.3Š2.7) (3) I need to install into a specific prefix and PyQt is > not easil

Re: [PyQt] [SOLVED] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Brian Kelley
Phil is putting out a new snapshot, but here are the details: this bug is encountered when Qt is build with no open ssl, if you don't want to wait for the snapshot or next release, you can do the following. Edit PyQt-*-4.9.1/sip/QtNetwork/qssl.sip You need to edit the bottom of the file so that

Re: [PyQt] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Phil Thompson
Hopefully this is fixed in tonight's PyQt snapshot. The bug is triggered if you are using a build of Qt v4.8.0 or later without support for OpenSSL. Thanks to Brian Kelley for helping to find this. Phil ___ PyQt mailing listPyQt@riverbankcomputing.

Re: [PyQt] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Brian Kelley
I'll do it now. Brian On 4/26/12 9:25 AM, "Phil Thompson" wrote: >Hmm - I'm beginning to think this is a memory corruption problem. > >Can you (and Brian, and anybody else with the problem) try the version of >sip at the tip of the hg repository - or wait until tonight's snapshot. > >This will

Re: [PyQt] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Phil Thompson
Hmm - I'm beginning to think this is a memory corruption problem. Can you (and Brian, and anybody else with the problem) try the version of sip at the tip of the hg repository - or wait until tonight's snapshot. This will include the name of the .sip file and line number in the error message. Can

Re: [PyQt] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 )

2012-04-26 Thread Brian Kelley
Interestingly I have the same issues on Ubuntu10 (64bit) and SLE10 (64bit) but my windows 32 bit build went fine, the only correlation here is this a 64 bit issue although RHEL5-64 works fine… I'll check windows64 with my build systems later today to see if that breaks as well. The basic conse