On Mon 30-Apr-07, Danny Pansters wrote:
> On Monday 30 April 2007 16:46:59 you wrote:
> > > It seems I can't retrieve a QString object containing non-ASCII
> > > characters.
> >
> > You can if you use unicode() instead of str().
>
> Yes that's obvious, but it may break other people's apps when usin
Hi,
I am having some serious problems with *PyQT4*,
when i run pyqt script, I always get 'Segmentation *fault*'.
the script is simple:
==
%less qttest.py
from *PyQt4* import QtGui, QtCore
import sys
if __name__ == '__main__':
app = QtGui.QApplication(sys.argv)
Date: Sun, 29 Apr 2007 17:43:53 +0200
From: Hans-Peter Jansen <[EMAIL PROTECTED]>
Subject: Re: [PyQt] question re Atext drag and drop in PyQt3
To: pyqt@riverbankcomputing.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Am Freitag, 27. April 2007 23:43 schrieb
On Monday 30 April 2007 14:50:29 Giovanni Bajo wrote:
> On 30/04/2007 9.11, Mark Summerfield wrote:
> > But I agree with the general point that using "import *" is reasonable
> > when you have a large library like PyQt4---providing that library has
> > sensible export behaviour. For example, I _ass
On Monday 30 April 2007 21:35:57 Hans-Peter Jansen wrote:
> Am Montag, 30. April 2007 16:22 schrieb Danny Pansters:
> > The code that does the video capturing is written in C and used in the
> > rest of the app as a python module (using SWIG to expose a dozen simple
> > control functions).
>
> You
On Monday 30 April 2007 16:46:59 you wrote:
> > It seems I can't retrieve a QString object containing non-ASCII
> > characters.
>
> You can if you use unicode() instead of str().
Yes that's obvious, but it may break other people's apps when using such a
patched dcopext module. I create and mainta
Am Montag, 30. April 2007 16:22 schrieb Danny Pansters:
>
> The code that does the video capturing is written in C and used in the
> rest of the app as a python module (using SWIG to expose a dozen simple
> control functions).
You may want to do yourself a favour and wrap that stuff with sip. Tha
On Mon 30-Apr-07, Danny Pansters wrote:
> Hi,
>
> It seems I can't retrieve a QString object containing non-ASCII characters.
You can if you use unicode() instead of str().
> I have a TV application (on FreeBSD) and it exports most of its functions
> via dcop. I now added functionality to retrie
Hi,
It seems I can't retrieve a QString object containing non-ASCII characters. I
have a TV application (on FreeBSD) and it exports most of its functions via
dcop. I now added functionality to retrieve (raw YUV) framedata over dcop,
the idea being to eventually write a minimal dcopclient in C++
On 30/04/2007 9.11, Mark Summerfield wrote:
But I agree with the general point that using "import *" is reasonable
when you have a large library like PyQt4---providing that library has
sensible export behaviour. For example, I _assume_ that the PyQt4
libraries will only export things with names
On Monday 30 April 2007 8:02 am, Mark Summerfield wrote:
> On Sun 29-Apr-07, Phil Thompson wrote:
> > The current SIP snapshot now supports the provision of handwritten code
> > for pickling wrapped classes. It also automatically pickles enums. It
> > does not have the usual pickle restriction of n
On Sun 29-Apr-07, Giovanni Bajo wrote:
> On 29/04/2007 6.25, Andreas Pakulat wrote:
> > Right, the motivation for the Qt.py package is simply convenience for
> > porting PyQt3 code. Which doesn't mean you should use it in new PyQt4
> > programs. Using something like this creates enough convience wh
On Sun 29-Apr-07, Phil Thompson wrote:
> The current SIP snapshot now supports the provision of handwritten code for
> pickling wrapped classes. It also automatically pickles enums. It does not
> have the usual pickle restriction of not being able to pickle nested types.
>
> The current PyQt4 snaps
13 matches
Mail list logo
