If you use the Python API to import the module then the init function
will
only be called once, no matter how many times it is imported. You were
calling the init function explicitly.
We prefer to link our module statically, rather than
as a .pyd, that's why we rely on the
Hello,
why does configure.py use an existing feature file, *by default*, if it
finds one? The usual behaviour of configure scripts is to recheck the status
of the whole system each time they're invoked. After a recompilation of Qt,
I'd expect configure -c make make install to be sufficient.
Phil Thompson [EMAIL PROTECTED] wrote:
why does configure.py use an existing feature file, *by default*, if it
finds one? The usual behaviour of configure scripts is to recheck the
status
of the whole system each time they're invoked. After a recompilation of
Qt,
I'd expect configure -c
Hi,
I noticed that Qt 3.3.5 has been released with some bugs
fix. I wonder does the new PyQt 3.15 supports Qt 3.3.5?
Thank you very much!
Huaicai
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
Huaicai Mo [EMAIL PROTECTED] wrote:
I noticed that Qt 3.3.5 has been released with some bugs fix. I wonder
does
the new PyQt 3.15 supports Qt 3.3.5?
It works for me.
--
Giovanni Bajo
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
I'm currently banging my head on a small, simple (in theory), fullscreen
app that I've written using a KApplication, KMainWindow, and a KHTMLPArt
view as the central widget.
The background of the page being displayed in the view is black, and I
wish for the whole screen to be black.
On Wednesday 07 September 2005 20:39, Brian Thomason wrote:
I'm currently banging my head on a small, simple (in theory), fullscreen
app that I've written using a KApplication, KMainWindow, and a KHTMLPArt
view as the central widget.
The background of the page being displayed in the view is
