Phil Thompson wrote:
> What version of Qt?
>
> Phil
It's version 2.3.0 non-commerical for Windows. My OS is Windows 2000
Professional SP4. Using this same version of Qt for a Ruby-based
implementation of a similar app I didn't experience the access
violation crashes when invoking the setCentralWi
Phil Thompson wrote:
> What version of Qt?
>
> Phil
It's version 2.3.0 non-commerical for Windows. My OS is Windows 2000
Professional SP4. Using this same version of Qt for a Ruby-based
implementation of a similar app I didn't experience the access
violation crashes when invoking the setCentralWi
Hope this post doesn't duplicate, as a Google Groups error happened
last attempt...
Phil Thompson wrote:
> What version of Qt?
>
> Phil
It's version 2.3.0 non-commerical for Windows. My OS is Windows 2000
Professional SP4. Using this same version of Qt for a Ruby-based
implementation of a simila
On Saturday 07 January 2006 1:06 pm, gregarican wrote:
> I noticed that when I invoked the setCentralWidget() method using PyQt
> 3.13 on Python 2.3.5 opening and closing a widget associated with a
> main window would result in a Win32 access violation crash after a
> couple of times. Here's a gene
I noticed that when I invoked the setCentralWidget() method using PyQt
3.13 on Python 2.3.5 opening and closing a widget associated with a
main window would result in a Win32 access violation crash after a
couple of times. Here's a generic snippet:
class Application_Window(QMainWindow):
def _
