problem solved.
/usr/include/qt4/QtWebKit/qwebsettings.h have
not JavascriptCanAccessClipboard.
correct NAME is JavaScriptCanAccessClipboard.
but i didn`t know why sip made this typo .
___
PyQt mailing listPyQt@riverbankcomputing.com
Hi,
On 28 May 2010, at 23:11, Scott Frankel wrote:
Hi all,
What's the best way to manage multiple database connections in an
application? Specifically, how can I manage which db connection is used for
models, queries, c.?
The documentation says that multiple connections can be
I will be out of the office starting 29/05/2010 and will not return until
07/06/2010.
contact
Narinder Kumar 0208 738 8871 (narinder.ku...@ba.com)
Ian Sherrington (88149)
matthew page 0208 738 3519 (matthew.p...@ba.com)
Greg Lakin (0208 738 3469 (greg.t.la...@ba.com)
--
This message is private
Using the 2-parameter version of addDatabase() fixes the errors on
launch. Thanks Colin.
Still searching for best ways to access multiple db connections (docs
say it's possible, but don't describe how), I finally came upon the
following two links.
This is an article by Jasmin
On 29/05/10 10:00, Phil Thompson wrote:
Fixed in the current PyQt snapshot - sort of. It assumes that the char *
refers to a '\0' terminated string, which may not be the case.
Although earlier versions didn't seem to crash, I don't think they worked
any better.
thanks phil
i've tried the new
Hi there
I'm trying py2exe to build an .exe for windows XP, from a PyQt4 with
database (mysql) access.
After follow all steps, resolve problems by googling, i end with a exe that
works, but when i run a module that
connects with mysql, i get the error:
Driver not loaded Driver not loaded
On sab, 2010-05-29 at 14:54 -0300, Mario Daniel Carugno wrote:
Hi there
I'm trying py2exe to build an .exe for windows XP, from a PyQt4 with
database (mysql) access.
After follow all steps, resolve problems by googling, i end with a exe
that works, but when i run a module that
On 29/05/10 17:37, Baz Walter wrote:
On 29/05/10 10:00, Phil Thompson wrote:
Fixed in the current PyQt snapshot - sort of. It assumes that the char *
refers to a '\0' terminated string, which may not be the case.
Although earlier versions didn't seem to crash, I don't think they worked
any
I've got a strange behaviour with some keypress events which I've been able to
workaround but I'd like to share in case it may be a bug in PyQt.
The situation is a bit complex: I execute a PyQt application using an xrdp (an
open source RDP implementation) server which is being accessed through
