Re: [PyKDE] BUG - disconnect
On Wednesday 06 November 2002 04:00 pm, Phil Thompson wrote: > > > > > > Thanks. Although it isn't usually necessary, it will be nice to have. > > There is a bug in PyQt with respect to connections being removed when the > > associated object has been deleted. But I'll try to post some example > > code within the week. > > > > Basically, if I create a parentless object and connect signals to it. > > Upon deletion of the object, any signals that would thereafter have gone > > to it result in a sip runtime error saying the C++ object has been > > deleted. > > This should now be fixed in tonight's SIP snapshot. You should re-build > PyQt with the new version. > > Phil Thank you. It will help a lot. --Kaleb ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] BUG - disconnect
On Monday 04 November 2002 1:59 pm, Kaleb Pederson wrote: > On Sunday 03 November 2002 12:13 pm, Phil Thompson wrote: > > On Tuesday 29 October 2002 12:46 am, Kaleb Pederson wrote: > > > Disconnect doesn't seem to work as expected. > > > > > > > > > > > > which are all very similar to the documentation examples. SIP can't > > > seem to tell which method really should be called, and None and 0 > > > aren't accepted as valid wild cards so I can't really give it the > > > parameters that I need. > > > > It just isn't supported. I've updated the TODO list and the > > documentation. > > Thanks. Although it isn't usually necessary, it will be nice to have. > There is a bug in PyQt with respect to connections being removed when the > associated object has been deleted. But I'll try to post some example code > within the week. > > Basically, if I create a parentless object and connect signals to it. Upon > deletion of the object, any signals that would thereafter have gone to it > result in a sip runtime error saying the C++ object has been deleted. This should now be fixed in tonight's SIP snapshot. You should re-build PyQt with the new version. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] qwidgetstack.sip bug
Hi Michael, That's why we all LOVE context diffs. I suggest: alias diff='diff -u5' Have a nice day, Hans-Peter On Wednesday 06 November 2002 17:21, Michael Lauer wrote: > Hi, > > - > %If (- Qt_3_0_0) > void addWidget(QWidget * /Transfer/,int); > %End > %If (Qt_3_0_0 -) > void addWidget(QWidget * /Transfer/,int = -1); > %End > - > > is wrong. It should be > - > %If (- Qt_3_0_0) > void addWidget(QWidget * /Transfer/,int); > %End > %If (Qt_3_0_0 -) > int addWidget(QWidget * /Transfer/,int = -1); > %End > - > > Yours, ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] qwidgetstack.sip bug
Hi, - %If (- Qt_3_0_0) void addWidget(QWidget * /Transfer/,int); %End %If (Qt_3_0_0 -) void addWidget(QWidget * /Transfer/,int = -1); %End - is wrong. It should be - %If (- Qt_3_0_0) void addWidget(QWidget * /Transfer/,int); %End %If (Qt_3_0_0 -) int addWidget(QWidget * /Transfer/,int = -1); %End - Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Problem building PyQt under debian (sid)
On Tue, Nov 05, 2002 at 01:46:45PM -0600, Michael Ledet wrote: > > I'm getting an error from build.py claiming that the compiler doesn't support > no_exceptions.. > > Any ideas? > ** > Checking to see if the C++ compiler supports -fno-exceptions. > ** > make: *** No rule to make target `/usr/mkspecs/linux-g++/qmake.conf', needed > by `Makefile'. Stop. > ** As you can see, this is a _path_ problem, not a compiler one (mkspecs is at /usr/share/qt, not /usr). You can either use the packages on unstable (python2.1-qt3 / python2.2-qt3), or get my source package to see what changes I've done to make PyQt compile on Debian's environment (This is not the only problem you will face). If you need packages for Stable, then: apt-get -b source python-qt3 # deb-src pointing to unstable Or wait a few days. I'm building a Stable compilation environment and will produce packages for stable/woody. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Problem building PyQt under debian (sid)
I'm getting an error from build.py claiming that the compiler doesn't support no_exceptions.. Any ideas? mledet@nature:~/downloads/PyQt-x11-gpl-3.4$ python2.2 build.py -p ./sip -l qt-mt -i /usr/include/qt -q /usr ** Building the GPL version of PyQt 3.4 for Python 2.2.2 on linux2. ** ** /usr/lib/python2.2/site-packages is the PyQt installation directory. ** ** /usr/include/python2.2 contains Python.h. ** ** ./sip will be used as the SIP code generator. ** ** /usr/include/python2.2 contains sipQt.h. ** ** /usr/lib/python2.2/site-packages contains the SIP module. ** ** /usr is the Qt base directory. ** ** /usr/include/qt contains qglobal.h. ** ** Qt 3.0.5 is being used. ** ** /usr/bin/qmake will be used to generate Makefiles. ** ** Qt thread support is enabled. ** ** /usr/bin/make will be used as the make program. ** ** Checking to see if the C++ compiler supports -fno-exceptions. ** make: *** No rule to make target `/usr/mkspecs/linux-g++/qmake.conf', needed by `Makefile'. Stop. ** The C++ compiler doesn't support -fno-exceptions. ** make: *** No rule to make target `/usr/mkspecs/linux-g++/qmake.conf', needed by `Makefile'. Stop. ** Error: /usr/bin/make failed with an exit code of 2. -- Michael Ledet Spire Network Services ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Qt designer static images and pyQt
On Tuesday 05 November 2002 11:40 pm, Amir Michail wrote: > Hi, > > I was wondering what the standard way of > including static images is in a pyQt application. > > I have tried including a static image in a dialog > designed by Qt designer and then using the -embed > option in pyuic (pyQt 3.1). However, this resulted in several problems: > > * it generated incorrect code (there's a missing str on a QString > comparison with a python string) > * even after fixing this, only the first 1/3 or so of the image appeared > correctly; the rest was garbled Can you send me an example .ui file? If you use a significantly smaller or larger image, is it still 1/3 that is ok? Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
