In other thread[1] Christian reported that the right QAbstractButton.clicked signal failed to connect with lambda and partial functions. Since the signal signature is "clicked(bool = false)" one would suppose that "button.clicked.connect(...)" would connect to the "clicked()" version of the signal. But due to a generation error not even explicitly connecting to it with "button.clicked[None].connect(...)" would work.
I fixed the problem in the commit Shiboken/33537a0e, which will register the signatures "clicked()" and "clicked(bool)", instead of just the latter. I wasn't unaware, but my fix could interfere with what is discussed with this PSEP. I need your comments on my change. If it should be reverted and put on a branch for future use after some decision is made regarding the signal behavior, or just leave it on HEAD as it is. On Fri, Nov 26, 2010 at 10:13 AM, Matti Airas <[email protected]> wrote: > On 24.11.2010 20:43, ext [email protected] wrote: > >> As another approach to dealing with the problem of undefined default >> signatures, could we just print a warning whenever the default signature is >> used for overloaded signals? This would have no effect on PySide semantics, >> and would, in my opinion, not even require a PSEP. > > What's the opinion on this one? Would this approach sufficiently solve the > issue? [1] http://lists.openbossa.org/pipermail/pyside/2010-December/001610.html _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
