Re: [PyKDE] QComboBox question...

2003-11-06 Thread Trevor Phillips
On Wednesday 05 November 2003 22:34, you wrote: > > Tnx for your response Trevor! I was already thinking in the same > direction... Seems a good way to do this. I don't know about a "good" way - but it's the only way I know of. It probably wouldn't be too hard to OOP up a new class inheriting q

Re: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Phil Thompson
On Thursday 06 November 2003 8:24 pm, Peter Kropf wrote: > I'm curious why you see static in the python library as an advantage? Because it should also solve the problem but wouldn't require changes to import statements. Phil > > -Original Message- > > From: Phil Thompson [mailto:[EMAIL

RE: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Peter Kropf
Title: RE: [PyKDE] Building PyQt as 1 shared library I'm curious why you see static in the python library as an advantage? > -Original Message- > From: Phil Thompson [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 06, 2003 9:19 AM > To: Peter Kropf; '[EMAIL PROTECTED]'; > [E

[PyKDE] Packaging PyKDE-3.8.0

2003-11-06 Thread Jim Bublitz
Just a brief note to packagers considering doing RPMs or Debian packages for PyKDE-3.8.0: 1. The doc viewer ("wabbit") is at PyKDE-3.8.0/docs/wabbit; the tarball installs a symlink in /usr/bin. It also needs to create a ".wabbit" directory in the user's home directory and install an rc file th

[PyKDE] Re: pyKDE error -no more

2003-11-06 Thread Jim Bublitz
On Thursday November 6 2003 09:25, Hannes Hauswedell wrote: > YESS!!! > it works! i had to add a -L infornt of /opt/kde3/libs too but > now it works! thank you so much for all your time and efforts! > really i apreciate. ok i will stop bugging you now ;-) > thanks and greetings > hannes hau

Re: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Phil Thompson
On Thursday 06 November 2003 4:58 pm, Peter Kropf wrote: > To start, merging qttable into qt was fairly easy. I modified qtmod.sip, > adding %Include qtable.sip. Then rebuilding PyQt resulted in the qtable > code being included and accessable from python. Instead of: > > from qttable import QTa

Re: [PyKDE] Python/pystate.c:423: failed assertion `autoInterpreterState'

2003-11-06 Thread Phil Thompson
On Thursday 06 November 2003 4:59 pm, michael ferraro wrote: > since upgrading to: > > qt-mac-free-3.2.2 > sip-mac-gpl-4.0pre3 > PyQt-mac-gpl-snapshot-20031027 > > on a DUAL 1.4 G4 running Panther > > I have been getting this message when I > sys.exit() or app.quit() my application. > > I have not

RE: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Peter Kropf
Title: Message I also had to comment out the   %Import qttablemod.sip in qtsqlmod.sip since the qtable definitions are coming from the qtmod.sip import.   -Original Message-From: Peter Kropf [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 8:58 AMTo: '[EMAIL PRO

RE: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Peter Kropf
Title: RE: [PyKDE] Building PyQt as 1 shared library To start, merging qttable into qt was fairly easy. I modified qtmod.sip, adding %Include qtable.sip. Then rebuilding PyQt resulted in the qtable code being included and accessable from python. Instead of:     from qttable import QTable t

[PyKDE] Python/pystate.c:423: failed assertion `autoInterpreterState'

2003-11-06 Thread michael ferraro
since upgrading to: qt-mac-free-3.2.2 sip-mac-gpl-4.0pre3 PyQt-mac-gpl-snapshot-20031027 on a DUAL 1.4 G4 running Panther I have been getting this message when I sys.exit() or app.quit() my application. I have not been able to find out what it means Anyone seen this before or know what I'm

[PyKDE] PyKDE-3.8 available

2003-11-06 Thread Jim Bublitz
The "just minutes ago" part of my PyKDE-3.8 announcement turns out to have been about 8 hours ago due to a problem with sending mail here - Phil already has the tarball up on the riverbankcomputing site (thanks!) Jim ___ PyKDE mailing list[EMAIL

[PyKDE] PyKDE-3.8 released

2003-11-06 Thread Jim Bublitz
Withing the last couple minutes I just emailed the PyKDE-3.8.0 release to Phil for posting on the riverbankcomputing site. Phil normally posts the tarballs quickly if he's available. I just noticed I forgot to remove one (large) file from the top-level directory, so I may need to send Phil a re

Re: [PyKDE] QImageIO class

2003-11-06 Thread Phil Thompson
On Thursday 06 November 2003 10:09 am, david wrote: > I would like to write an image into memory but it don't work, QImageIO > class don't exist with Qt 3.1.0 and PyQt 3.5 ? > > > from qt import * > > iio = QImageIO() > im = QImage() > im = pixmap() //convert to image > iio.setImage(im) There doe

Re: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Ulrich Berning
Phil Thompson schrieb: On Wednesday 05 November 2003 10:57 pm, Peter Kropf wrote: Does anyone know if it's possible to build PyQt so that there is one shared library that contains all the code instead of the 8 (libqtcanvascmodule.so, libqtcmodule.so, libqtextcmodule.so, libqtnetworkcmodule.so,

[PyKDE] QImageIO class

2003-11-06 Thread david
I would like to write an image into memory but it don't work, QImageIO class don't exist with Qt 3.1.0 and PyQt 3.5 ? from qt import * iio = QImageIO() im = QImage() im = pixmap() //convert to image iio.setImage(im) Thanks for your help. David __

Re: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Phil Thompson
On Wednesday 05 November 2003 10:57 pm, Peter Kropf wrote: > Does anyone know if it's possible to build PyQt so that there is one shared > library that contains all the code instead of the 8 (libqtcanvascmodule.so, > libqtcmodule.so, libqtextcmodule.so, libqtnetworkcmodule.so, > libqtsqlcmodule.so,

Re: [PyKDE] Building PyQt as 1 shared library

2003-11-06 Thread Ulrich Berning
Peter Kropf schrieb: Does anyone know if it's possible to build PyQt so that there is one shared library that contains all the code instead of the 8 (libqtcanvascmodule.so, libqtcmodule.so, libqtextcmodule.so, libqtnetworkcmodule.so, libqtsqlcmodule.so, libqttablecmodule.so, libqtuicmodule.so,