Bug 431 – QMetaProperty::read: Unable to handle unregistered datatype 'str' for property

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 431 - QMetaProperty::read: Unable to handle unregistered datatype 'str' for property

Summary:

QMetaProperty::read: Unable to handle unregistered datatype 'str' for property

Status:	CLOSED FIXED

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

Importance:	P3 critical
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-10-22 08:01 EEST by Matti Airas
Modified:	2010-11-25 17:48 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Ported example (4.12 KB, application/x-gzip) 2010-10-22 08:01 EEST, Matti Airas	Details
example changed to works with PySide (4.12 KB, application/x-gzip) 2010-10-22 15:28 EEST, renato filho	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-22 08:01:09 EEST

When trying to port PyQt's examples/declarative/modelviews/objectlistmodel
(directory attached), I get the following (using git HEAD as of 2010-10-22):

QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QDeclarativeExpression: Expression "(function() { return model.modelData.color
})" depends on non-NOTIFYable properties: 
    DataObject::color
QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QDeclarativeExpression: Expression "(function() { return model.modelData.color
})" depends on non-NOTIFYable properties: 
    DataObject::color
QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QDeclarativeExpression: Expression "(function() { return model.modelData.color
})" depends on non-NOTIFYable properties: 
    DataObject::color
QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QDeclarativeExpression: Expression "(function() { return model.modelData.color
})" depends on non-NOTIFYable properties: 
    DataObject::color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color


When I run the script for a second time (so that objectlistmodel_rc.py already
exists), I get:

QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
QMetaProperty::read: Unable to handle unregistered datatype 'str' for property
'DataObject::color'
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color
qrc:view.qml:53: ReferenceError: Can't find variable: name
qrc:view.qml:52: Unable to assign [undefined] to QColor color


Deleting *.pyc gives you the original error message again.

Comment 1 Matti Airas 2010-10-22 08:01:35 EEST

Created attachment 122 [details]
Ported example

Comment 2 renato filho 2010-10-22 15:27:19 EEST

I made some changes on your example to get this working with Pyside I do not
know if this is a problem with PySide or not. Can you check if these
modifications make some sense or not?

The string conversions was fixed on Pyside commit:

commit 8e1e25a631d3e697ea795d66c8ed7e8fbbf7c6dd
Author: renatofilho <renato.filho@openbossa.org>
Date:   Fri Oct 22 14:25:37 2010 -0300

Comment 3 renato filho 2010-10-22 15:28:29 EEST

Created attachment 123 [details]
example changed to works with PySide

Comment 4 renato filho 2010-10-22 15:29:04 EEST

If this changes does not make sense. could you report new bugs for this?

Comment 5 renato filho 2010-11-25 17:48:16 EET

released on 1.0.0~beta1