Bug 442 – Error message when connecting a signal originating from a QML object

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 442 - Error message when connecting a signal originating from a QML object

Summary:

Error message when connecting a signal originating from a QML object

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtDeclarative
Version:	HEAD
Platform:	All All

Importance:	P3 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-10-28 10:05 EEST by Matti Airas
Modified:	2010-11-25 17:48 EET (History)
CC List:	0 users

See Also:

Attachments
Example application (657 bytes, application/x-gzip) 2010-10-28 10:05 EEST, Matti Airas	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matti Airas 2010-10-28 10:05:13 EEST

Created attachment 130 [details]
Example application

This is interesting:

When I connect a signal of a QML object to a Python function, I get the
following error message:

You can't add dynamic signals or slots on an object originated from C++.

OK, that's not so interesting, but the fact that the slot still gets called is.
The attached example program prints "foo" whenever the gray rectangle is
clicked (although the signal appears to be emitted multiple times, which could
be a bug either in QML or in PySide).

Comment 1 renato filho 2010-10-28 21:44:14 EEST

fixed on pyside commit:
commit bd8239b1cd99d25c26eb99a051072254342ab0bb
Author: renatofilho <renato.filho@openbossa.org>
Date:   Thu Oct 28 16:28:43 2010 -0300

Comment 2 renato filho 2010-11-25 17:48:18 EET

released on 1.0.0~beta1