Is'n it nice to be able to answer ones own questions? Scanning through
the OBB 0.5's sources gave me the answer.
For the record, the answer is to pass the flags in the class init.
FLAGS = Qt.WStyle_StaysOnTop \
+Qt.anotherflag \
+..
class myDialog(QDialog):
def
Hi,
I currently trying to set up signals and slots in my application I
understand the principals and have read many examples but I am unable to
get it working on my own could someone possibly help me out :) as this
is only a basic test I am hoping to pass objects later but that is
another step :)
I heard Stuart Bronk said:
I have a Widget and a class called Figure I am attempting to connect
the method Figure.loadQ with the Widgets loadQ method but I cannot
seem to get it to work
...
self.connect(self.Figure, SIGNAL(loadQ()), self.loadQ())
Okay, two things.
To start with, if
On Wednesday 05 March 2003 5:06 pm, Paul F. Kunz wrote:
One of my users is having a problem building my software with PyQt
3.5 and the Qt 3.0.3 that came with his Red Hat 7.3 installation. Qt
3.0.3 doesn't appear to be supported by sip, so he tried 3.0.2 and
3.0.4 but got the following
Ok, I'll ask it, what version of sip are you using?
I've recently compiled and install PyQt on two diff.
Rh7.3 machines with Qt 3.0.3 with no problems.
Make sure you are using current PyQt and Sip.
Here's a list of the files I used..
rpm -q qt = qt-3.0.3.11
On Wednesday 05 March 2003 5:28 pm, Stuart Bronk wrote:
Hi,
I currently trying to set up signals and slots in my application I
understand the principals and have read many examples but I am unable to
get it working on my own could someone possibly help me out :) as this
is only a basic test
On Wed, 05 Mar 2003 18:13:49 +, Phil Thompson [EMAIL PROTECTED] said:
What makes you think that sip doesn't support Qt 3.0.3?
Qt 3.0.3 is not in the version.sip file...
%Timeline {Qt_1_43
Qt_2_00 Qt_2_1_0 Qt_2_2_0 Qt_2_3_0 Qt_2_3_1
Qt_3_0_0
I heard Frederick Polgardy Jr said:
self.connect(self.Figure, PYSIGNAL(loadQ()), self.loadQ)
Of course, what you're left with is an endless loop. :)
I'm not sure. It depends on what the loadQ slot on -self- (as opposed to
self.Figure) does, right...?
-- S.
On Wed, 05 Mar 2003 11:20:18 -0700, Ken Godee [EMAIL PROTECTED] said:
Ok, I'll ask it, what version of sip are you using?
3.5
I've recently
compiled and install PyQt on two diff. Rh7.3 machines with Qt 3.0.3
with no problems.
My user also had no problems with PyQt. The problem
On Wed, 05 Mar 2003 09:06:16 -0800, Paul F. Kunz [EMAIL PROTECTED] said:
One of my users is having a problem building my software with
PyQt 3.5 and the Qt 3.0.3 that came with his Red Hat 7.3
installation. Qt 3.0.3 doesn't appear to be supported by sip, so he
tried 3.0.2 and 3.0.4 but
On Wednesday 05 March 2003 6:26 pm, Paul F. Kunz wrote:
On Wed, 05 Mar 2003 18:13:49 +, Phil Thompson
[EMAIL PROTECTED] said:
What makes you think that sip doesn't support Qt 3.0.3?
Qt 3.0.3 is not in the version.sip file...
%Timeline {Qt_1_43
Qt_2_00
Thanks for the suggestion, unfortunately it is now returning a different
error.
My widget code is now like this:
self.Figure = Figure.Figure() # instantiate Figure
self.connect(self.Figure, PYSIGNAL(sigloadQ), self.loadQ)
Figure class is this:
def loadQ():
On Wed, 05 Mar 2003 20:16:43 +, Phil Thompson [EMAIL PROTECTED] said:
Versions are only defined if they are needed. They are needed if a
version of Qt changes the API is some way that affects PyQt. (Take
Trolltech's claims about maintaining binary compatibility with a
large sack of
On Wednesday 05 March 2003 8:19 pm, Paul F. Kunz wrote:
On Wed, 05 Mar 2003 20:16:43 +, Phil Thompson
[EMAIL PROTECTED] said:
Versions are only defined if they are needed. They are needed if a
version of Qt changes the API is some way that affects PyQt. (Take
Trolltech's claims
On Wednesday 05 March 2003 8:19 pm, Stuart Bronk wrote:
Thanks for the suggestion, unfortunately it is now returning a different
error.
My widget code is now like this:
self.Figure = Figure.Figure() # instantiate Figure
self.connect(self.Figure, PYSIGNAL(sigloadQ), self.loadQ)
Hello, I'm having a problem here that I hope someone can solve. I'm
using qtcanvas and want to have a QCanvasSprite item that shows a single
image, but no mather what I do I get a segmentation fault (and no other
output). I'm sure that the picture I'm trying to show is valid
(isValid() on the
I'm running RH7.3 + updates. One of the wonderful things about that
distribution is PyQt-3.1-2 has a bug with QInputDialog.getText().
Namely, the 'parent' argument always complains of invalid type.
I found: http://www.river-bank.demon.co.uk/download/snapshots/PyQt/ChangeLog
which has:
Lars Kirkhus [EMAIL PROTECTED] writes:
What am I doing wrong?
Found the answer: add the pixmaparray to self.
Note to self - search the archive before asking next time, sorry.
Lars Kirkhus
___
PyKDE mailing list[EMAIL PROTECTED]
On 05-Mar-03 Eli Carter wrote:
I'm running RH7.3 + updates. One of the wonderful things about
that distribution is PyQt-3.1-2 has a bug with
QInputDialog.getText(). Namely, the 'parent' argument always
complains of invalid type.
I found:
Phil,
After playing with Kugar, I decided to go ahead and
give PyQt printing a try.
As everyone says take a look at the example code.
The first I tried was examples3/mdi.py but the printDoc
method of the MDIWindow class does not work as written in
the example code.
Here's the changes needed to
20 matches
Mail list logo
