On 16.12.2010 17:55, ext [email protected] wrote:
Hi,
thanks for the answers!
I didn't read about the default signals in the archive, but surely will dig
them out when I find some time.
The basic idea here is that for functions having overloaded signatures,
the default signature is not well-defined and also not necessarily the
same as in PyQt. For example, QtGui.QComboBox has alternate int and
unicode signatures. If you connect without defining the signature:
self.cbox.activated.connect(myfunc)
you might not know which signal gets connected without trying. Instead,
whenever connecting overloaded signals, you should define the specific
signal:
self.cbox.activated[unicode].connect(myfunc)
In the next sprint, we're going to make PySide print a warning to STDERR
whenever such an ambiguous signal connection is made.
The test cases were attached in the original email, I've re-added them to this
email and hope that some may be of use.
Thanks - I suppose Hugo will take a look at these.
I'm pretty impressed of PySide and Qt I must say. After the 1.0 release PySide
should be elected to be the Python default GUI framework. PySide + Qt light
years ahead of the Tcl/Tk wrapper and the LGPL version should make it possible
licensing wise.
When this happens Apple will remove Python from the default install in Mac OS
X, though ;-)
Thank you for the praise! Personally, I'm more than happy even if it
just becomes the de-facto standard. :-D
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
