QQmlError.object now holds the scope object that caused exceptions.
authorMark Visser <mjmvisser@gmail.com>
Tue, 30 Apr 2013 18:12:37 +0000 (14:12 -0400)
committerThe Qt Project <gerrit-noreply@qt-project.org>
Wed, 8 May 2013 08:46:13 +0000 (10:46 +0200)
commit13afb2b49daec9f5f65dc9a99151c91d685dce13
tree79c00dec10a6d90152213c0a85fafe6a9a480a95
parent22fc92cf9187460785a05e31620823fe8afe5eab
QQmlError.object now holds the scope object that caused exceptions.

Exception errors sent via QQmlEngine::warnings lacked a pointer to the
containing scope. I added an object property to QQmlError, and the
necessary code to fill it with the QObject* scope from binding exception
callbacks.

Task-number: QTBUG-30930
Change-Id: I2a987e8cefc3a2a474d338893e9ebcb77c167adf
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
src/qml/qml/qqmlerror.cpp
src/qml/qml/qqmlerror.h
src/qml/qml/qqmljavascriptexpression.cpp
src/qml/qml/qqmljavascriptexpression_p.h
src/qml/qml/qqmlproperty.cpp
src/qml/qml/v4/qv4bindings.cpp
src/qml/qml/v8/qv8bindings.cpp