Re: [PyKDE] weird PyQt bug: memory corruption?

2005-04-28 Thread Giovanni Bajo
Ümit Öztosun [EMAIL PROTECTED] wrote: What happens in my full application is an AttributeError while trying to call QScrollView.viewport().setBackgroundMode, because the name does not exit (the object is a QObject instead of a QWidget). Hi, Although I am unable to reproduce the problem, a

Re: [PyKDE] weird PyQt bug: memory corruption?

2005-04-28 Thread Phil Thompson
On Thursday 28 April 2005 2:18 pm, Giovanni Bajo wrote: Ümit Öztosun [EMAIL PROTECTED] wrote: What happens in my full application is an AttributeError while trying to call QScrollView.viewport().setBackgroundMode, because the name does not exit (the object is a QObject instead of a

Re: [PyKDE] weird PyQt bug: memory corruption?

2005-04-25 Thread Giovanni Bajo
Phil Thompson [EMAIL PROTECTED] wrote: I see the same behaviour using the same versions. However with current snapshots the behaviour is as expected. Those versions are just a few modifies apart from the current snapshots, right? I don't want to be dense here, but if you are not sure that you

Re: [PyKDE] weird PyQt bug: memory corruption?

2005-04-24 Thread Phil Thompson
On Thursday 21 April 2005 7:09 pm, Giovanni Bajo wrote: Hello, I have found a very weird bug with PyQt, which might be some sort of memory corruption thus hard to reproduce. I'm using Qt 3.3.4, PyQt 3.14.1, SIP 4.2.1, under Windows. This is the minimal snippet (took me two hours to reduce

Re: [PyKDE] weird PyQt bug: memory corruption?

2005-04-21 Thread Ümit Öztosun
Can anybody reproduce this? Phil, do you have any idea about what might be causing this? What happens in my full application is an AttributeError while trying to call QScrollView.viewport().setBackgroundMode, because the name does not exit (the object is a QObject instead of a QWidget).