On Feb 28, 10:45 am, Phil Thompson <[EMAIL PROTECTED]>
wrote:
> On Wednesday 28 February 2007 9:26 am, [EMAIL PROTECTED] wrote:
>
>
>
>
>
> > On Feb 28, 10:22 am, Phil Thompson <[EMAIL PROTECTED]>
>
> > wrote:
> > > On Wednesday 28 February 2007 9:00 am, [EMAIL PROTECTED] wrote:
> > > > On Feb 28,
On Wednesday 28 February 2007 9:26 am, [EMAIL PROTECTED] wrote:
> On Feb 28, 10:22 am, Phil Thompson <[EMAIL PROTECTED]>
>
> wrote:
> > On Wednesday 28 February 2007 9:00 am, [EMAIL PROTECTED] wrote:
> > > On Feb 28, 9:07 am, [EMAIL PROTECTED] wrote:
> > > > On Feb 28, 8:56 am, Phil Thompson <[EMAI
On Feb 28, 10:22 am, Phil Thompson <[EMAIL PROTECTED]>
wrote:
> On Wednesday 28 February 2007 9:00 am, [EMAIL PROTECTED] wrote:
>
>
>
>
>
> > On Feb 28, 9:07 am, [EMAIL PROTECTED] wrote:
> > > On Feb 28, 8:56 am, Phil Thompson <[EMAIL PROTECTED]>
>
> > > wrote:
> > > > On Tuesday 27 February 2007 1
On Wednesday 28 February 2007 9:00 am, [EMAIL PROTECTED] wrote:
> On Feb 28, 9:07 am, [EMAIL PROTECTED] wrote:
> > On Feb 28, 8:56 am, Phil Thompson <[EMAIL PROTECTED]>
> >
> > wrote:
> > > On Tuesday 27 February 2007 11:09 pm, shredwheat wrote:
> > > > When your programs stops with the error, it s
On Feb 28, 9:07 am, [EMAIL PROTECTED] wrote:
> On Feb 28, 8:56 am, Phil Thompson <[EMAIL PROTECTED]>
> wrote:
>
> > On Tuesday 27 February 2007 11:09 pm, shredwheat wrote:
>
> > > When your programs stops with the error, it should also be printing a
> > > stack trace. This is a list of all the func
On Feb 28, 8:56 am, Phil Thompson <[EMAIL PROTECTED]>
wrote:
> On Tuesday 27 February 2007 11:09 pm, shredwheat wrote:
>
> > When your programs stops with the error, it should also be printing a
> > stack trace. This is a list of all the functions that have been called
> > when Python had the probl
On Tuesday 27 February 2007 11:09 pm, shredwheat wrote:
> When your programs stops with the error, it should also be printing a
> stack trace. This is a list of all the functions that have been called
> when Python had the problem.
>
> You shouldn't have to do anything extra to get the stack trace.
When your programs stops with the error, it should also be printing a
stack trace. This is a list of all the functions that have been called
when Python had the problem.
You shouldn't have to do anything extra to get the stack trace.
--
http://mail.python.org/mailman/listinfo/python-list
shredwheat napĂsal(a):
> On Feb 27, 3:35 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> > I don't see any QPaintDevice here. Where does that come from? You need to
> > give more information, a stack trace and a reduced example exhibiting the
> > behaviour.
>
> QWidget is derived from QPaintDe
On Feb 27, 3:35 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> I don't see any QPaintDevice here. Where does that come from? You need to
> give more information, a stack trace and a reduced example exhibiting the
> behaviour.
QWidget is derived from QPaintDevice, under Qt, no widgets can be
i
[EMAIL PROTECTED] wrote:
> On Feb 27, 11:56 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
>> > Yes that I can deduce, but why I'm asking is why it's different on
>> > Windows and Linux. Should it not be platform independent?
>>
>> It should be. I've got no idea why it seems to work on windows
On Feb 27, 11:56 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> > Yes that I can deduce, but why I'm asking is why it's different on
> > Windows and Linux. Should it not be platform independent?
>
> It should be. I've got no idea why it seems to work on windows but I can say
> one thing for su
>
> Yes that I can deduce, but why I'm asking is why it's different on
> Windows and Linux. Should it not be platform independent?
It should be. I've got no idea why it seems to work on windows but I can say
one thing for sure: that would be an artifact that you shouldn't rely on.
In Qt, you _alw
On Feb 27, 11:46 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Hi all,
>
> > I have a python script that works without any problem on Windows but
> > with error:
>
> > QPaintDevice: Must construct a QApplication before a QPaintDevice
>
> > on Linux.
>
> > Where co
[EMAIL PROTECTED] wrote:
> Hi all,
>
> I have a python script that works without any problem on Windows but
> with error:
>
> QPaintDevice: Must construct a QApplication before a QPaintDevice
>
> on Linux.
>
> Where could be the problem?
This is the problem:
You Must construct a QApplication
15 matches
Mail list logo