Re: [PyKDE] overloading events with qt designer and pyqt

2005-06-29 Thread Frank Stüss
thanks for all advice. As mentioned before in this list by another smart one, a conveniend way was this: in designer i generate a custom widget with class QHBox and policy 'expanding' and then use it as a placeholder. My final signal/event catching widget is constructed 'by hand' as child of t

Re: [PyKDE] Windows systray application

2005-06-29 Thread basse
Rob Knapp kirjoitti viestissään (lähetysaika tiistai, 28. kesäkuuta 2005 17:26): > AFAIK, QT doesn't currently have a class that allows this. You will > need to use the win32api call SHELL_NOTIFYICON to create the icon, and > then I used the winEvent (I think, it's been about 2 years) to capture

Re: [PyKDE] Typecasting problems with PyQt embedded in Scribus

2005-06-29 Thread Jim Bublitz
On Wednesday 29 June 2005 19:34, Henning Schröder wrote: > Hi! > > Scribus is a free DTP application which is coded in C++ and Qt and > provides scripting > with Python. > A Python script can import the qt module and access the data from the > running application as far as it is reachable with the

[PyKDE] Typecasting problems with PyQt embedded in Scribus

2005-06-29 Thread Henning Schröder
Hi! Scribus is a free DTP application which is coded in C++ and Qt and provides scripting with Python. A Python script can import the qt module and access the data from the running application as far as it is reachable with the Qt-object system (qApp.children(), ..) Unfortunately automatic typeca

[PyKDE] Re: Memory leak & segfault with deleteLater

2005-06-29 Thread Phil Thompson
On Tuesday 28 June 2005 11:38 am, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > > Should be fixed in tonight's SIP snapshot. The cyclic garbage collector > > was > > > ignoring the extra reference to wrappers of objects owned by C++. > > Thanks, I just verified that this fixes m

Re: [PyKDE] [PATCH] Fix compilation of PyKDE snapshot20050628

2005-06-29 Thread Sebastian Kügler
On Wednesday 29 June 2005 22:13, Jim Bublitz wrote: > On Wednesday 29 June 2005 12:18, Sebastian Kügler wrote: > There are some compiler/distribution related bugs I haven't fixed yet > - QList is one and gcc4 stuff is another. I'll get to these as soon > as possible. Thanks, to clarify: it already

Re: [PyKDE] [PATCH] Fix compilation of PyKDE snapshot20050628

2005-06-29 Thread Jim Bublitz
On Wednesday 29 June 2005 12:18, Sebastian Kügler wrote: > Hi Jim, > > On Tuesday 28 June 2005 23:25, Jim Bublitz wrote: > > The latest sip snapshot this was tested against was the 06/05 > > snapshot. I haven't done a lot of testing with this, so please test > > and report any problems. This snapsh

[PyKDE] [PATCH] Fix compilation of PyKDE snapshot20050628

2005-06-29 Thread Sebastian Kügler
Hi Jim, On Tuesday 28 June 2005 23:25, Jim Bublitz wrote: > The latest sip snapshot this was tested against was the 06/05 > snapshot. I haven't done a lot of testing with this, so please test > and report any problems. This snapshot still requires gcc3.3. I got a couple of the following errors co

Re: [PyKDE] overloading events with qt designer and pyqt

2005-06-29 Thread Torsten Marek
Frank Stüss schrieb: >>I'm not sure if that's really what you want, but if you'd like to use >>qt-designer and hand-coded additions at the same time, you can create >>your UI / widgets using qt-designer and then subclassing that UI in >>another file and overload the (paint)event. That way you can s

[PyKDE] Latest PyKDE Snapshot

2005-06-29 Thread Phil Thompson
Jim's latest PyKDE snapshot is now in the snapshot's directory. Phil ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

Re: [PyKDE] Re: Bug with QScrollView viewport binding

2005-06-29 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: >> I understand the technical problem, but I believe it is a right >> expectation that any call to QScrollView.viewport() return a >> QWidget, as documented. The fact that thousands lines away I happen >> to have a QObject reference to the same object shoul

Re: [PyKDE] Re: Bug with QScrollView viewport binding

2005-06-29 Thread Phil Thompson
On Wednesday 29 June 2005 4:07 pm, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > >>> Yes - but they aren't in existence at the same time. > >>> [...] > >>> Using a temporary name to keep a reference to sv.viewport() solves the > >>> problem. > >> > >> Then you have the inverse p

Re: [PyKDE] Re: Bug with QScrollView viewport binding

2005-06-29 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: >>> Yes - but they aren't in existence at the same time. >>> [...] >>> Using a temporary name to keep a reference to sv.viewport() solves the >>> problem. >> >> Then you have the inverse problem: >> >> -- >> from

Re: [PyKDE] Handling exceptions in SIP

2005-06-29 Thread Phil Thompson
On Wednesday 29 June 2005 3:06 pm, Denis S. Otkidach wrote: > On Sun, 26 Jun 2005 23:05:33 +0100 > > Phil Thompson <[EMAIL PROTECTED]> wrote: > > Support for this is in tonight's snapshot - some changes to what I > > described above, but nothing sigificant. > > > > Support for converting Python exc

[PyKDE] Re: Memory leak & segfault with deleteLater

2005-06-29 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: > I think one way around the problem is to avoid the extra reference to the > Python object and move the data that it contains into a separate data > structure. In other words, weaken the link between the Python world and > the C++ world. My concern would t

Re: [PyKDE] Re: Bug with QScrollView viewport binding

2005-06-29 Thread Phil Thompson
On Wednesday 29 June 2005 3:21 pm, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > > Yes - but they aren't in existence at the same time. > > [...] > > Using a temporary name to keep a reference to sv.viewport() solves the > > problem. > > Then you have the inverse problem: > > --

[PyKDE] Re: Bug with QScrollView viewport binding

2005-06-29 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: > Yes - but they aren't in existence at the same time. > [...] > Using a temporary name to keep a reference to sv.viewport() solves the > problem. Then you have the inverse problem: -- from qt import * app = QA

[PyKDE] Re: Bug with QScrollView viewport binding

2005-06-29 Thread Phil Thompson
On Wednesday 29 June 2005 1:56 pm, Giovanni Bajo wrote: > Hello, > > --- > from qt import * > > app = QApplication([]) > sv = QScrollView(None) > w = QWidget(sv.viewport()) > > print sv.viewport() is w.parent() > print sv.viewport(), w.parent() > print sv.viewport().widt

Re: [PyKDE] Handling exceptions in SIP

2005-06-29 Thread Denis S. Otkidach
On Sun, 26 Jun 2005 23:05:33 +0100 Phil Thompson <[EMAIL PROTECTED]> wrote: > Support for this is in tonight's snapshot - some changes to what I described > above, but nothing sigificant. > > Support for converting Python exceptions to C++ exceptions in Python > re-implementations of C++ virtua

[PyKDE] Bug with QScrollView viewport binding

2005-06-29 Thread Giovanni Bajo
Hello, --- from qt import * app = QApplication([]) sv = QScrollView(None) w = QWidget(sv.viewport()) print sv.viewport() is w.parent() print sv.viewport(), w.parent() print sv.viewport().width() print w.parent().width() --- This outputs:

Re: [PyKDE] Qt 4 and python

2005-06-29 Thread Torsten Marek
Mark Saward schrieb: > Hi, > > Will pyqt work with Qt4 in windows as well? > > I'm hoping I can develop open source cross platform python/qt apps now that > this has been released. > > Mark > Hi Mark, have a look at http://www.riverbankcomputing.co.uk/pyqt/roadmap.php It says that a GPL vers

[PyKDE] QLineEdit focusInEvent() & setCursorPosition() problems

2005-06-29 Thread Danu Kusmana
I have notice several things after I reimplement focusInEvent(): 1. The cursor focus on QLineEdit widget is not blinking 2. eventhough I use setCursorPosition(0) after I entered some value to the line edit the cursor position at index 0 is start after the value I had entered I don't know if I do s