In my opinion is mandatory use of signature for all signals not only one with overloads because new signatures can be create in new versions of the Qt API then you will have you program broken.
On Wed, Nov 24, 2010 at 8:39 AM, Matti Airas <[email protected]> wrote: > On 23.11.2010 23:42, ext Chris Morgan wrote: >> >> I think it's well worth while specifying how multiple arguments will >> work, which may not necessarily be obvious - signal.activated[unicode, >> int].connect(myfunc) (gives __getitem__ a tuple, no need for extra () >> around it). > > OK, I'll add that (although this PSEP is not about specifying the complete > signal connection syntax, but just a specific special case). > >> If the target function has been decorated with QtCore.Slot, specifying >> the signature/s it wants, I also think it would be nice if >> signal.activated.connect(target) would use that/those rather than >> raising an error. I think this is necessary because you can have more then one signal signature which match with the slot signature, and like I told before, if a new signal or slot was create in a new version of your code or Qt API, you can get a unacceptable behavior in your program BR -- Renato Araujo Oliveira Filho Instituto Nokia de Tecnologia - INdT Mobile: +55 (81) 8704-2144 _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
