Using RTTI sounds like a better idea. Cleaner, more cpp like. Thanks, Phil.
On Wednesday 24 September 2003 10:10, Phil Thompson wrote:
> On Wednesday 24 September 2003 6:04 pm, Patrick Stinson wrote:
> > in progression:
> >
> > Does the %ConvertToSubClassCode directive require some sort of class
>
great, thanks Jim. I think I'll get it now.
On Wednesday 24 September 2003 09:39, Jim Bublitz wrote:
> On Wednesday September 24 2003 10:04, Patrick Stinson wrote:
> > in progression:
> >
> > Does the %ConvertToSubClassCode directive require some sort of
> > class identification mechanism to be wr
I'm running a self compiled PyQT-GPL-3.8 against Python-2.2.1 and Qt-3.1.1 on
a SuSE-8.1 box. I'm getting a SegV. The code is this:
---
from qt import *
class Model(QObject):
def __init__( self, *args ):
apply( QObject.__init__, (self,) + args )
self.currentImageList = []
On Wednesday 24 September 2003 6:04 pm, Patrick Stinson wrote:
> in progression:
>
> Does the %ConvertToSubClassCode directive require some sort of class
> identification mechanism to be written into the original cpp library code?
> QEvent returns an enumerated value in type(), as well ass QApplica
On Wednesday September 24 2003 10:04, Patrick Stinson wrote:
> in progression:
> Does the %ConvertToSubClassCode directive require some sort of
> class identification mechanism to be written into the original
> cpp library code? QEvent returns an enumerated value in
> type(), as well ass QApplicat
Hi
The release of PyQwt-3.8 is delayed because of the many new features that
are being added to the underlying Qwt library.
To help users who want to switch to PyQt-win-nc-3.8 and Python-2.3, I have
built a PyQwt_Qt230-3.7b.win32-py2.3.exe.
For installation instructions, see: http://pyqwt.source
in progression:
Does the %ConvertToSubClassCode directive require some sort of class
identification mechanism to be written into the original cpp library code?
QEvent returns an enumerated value in type(), as well ass QApplication and
some others, and QObject has QObject::className() that retur
I heard Tony Cappellini said:
> I was going through the pyQT tutorials when PYSIGNAL was used for the
> first time in Tutorial 1-7.
> Unfortunately the tutorial does not really explain what PYSIGNAL is
> and when it is needed, and I don't see any references in PyQT Doc for
> PYSIGNAL.
Ah, maybe
I was going through the pyQT tutorials when PYSIGNAL was used for the first
time in Tutorial 1-7.
Unfortunately the tutorial does not really explain what PYSIGNAL is and
when it is needed, and I don't see any references in PyQT Doc for PYSIGNAL.
Would someone help me out with this ?
thanks
On Wednesday 24 September 2003 15:46, Phil Thompson wrote:
> Should emit() take a variable number of arguments rather than a single
> tuple? Maybe, but it's too late to change now.
OK, that makes sense. :o)
--
> eatapple
core dump
___
PyKDE mailing li
> What do you get when you "print media"? If you get a PK_MediaLayer instance
> then maybe you haven't implemented %ConvertToSubClassCode properly.
I get a PK_MediaLayer instance. Ok, then, that would make sense. I''l check
that code tag...
> What versions are you using?
[EMAIL PROTECTED] ajol
On Wednesday 24 September 2003 8:02 am, Derek Fountain wrote:
> This might be a general Python newbie question. But it's confusing me in a
> PyQt context. :o)
>
> I have a slot in a class which receives a list of images. It adds that list
> to it's existing list, then sends off a signal saying the
This might be a general Python newbie question. But it's confusing me in a
PyQt context. :o)
I have a slot in a class which receives a list of images. It adds that list to
it's existing list, then sends off a signal saying the existing list has
changed:
currentImageList = []
def slotIn
13 matches
Mail list logo
