summaryrefslogtreecommitdiff
path: root/doc/src/snippets/qtquick1/qtbinding/functions-cpp
diff options
context:
space:
mode:
authorKent Hansen <kent.hansen@nokia.com>2012-01-18 07:03:48 +0100
committerQt by Nokia <qt-info@nokia.com>2012-02-02 12:07:13 +0100
commit52b77f94ab193c40096a5a3c106fcb2128085a30 (patch)
treeab6559cbcfc9babead88477d798e15679c0f69eb /doc/src/snippets/qtquick1/qtbinding/functions-cpp
parentfe6173c580ea58529d3b784c8396eabe3a394e85 (diff)
downloadqtdeclarative-52b77f94ab193c40096a5a3c106fcb2128085a30.tar.gz
Remove QJSEngine::undefinedValue() function
Rationale: It's strange to have an undefined value factory function. There should just be one way of constructing undefined values: By passing UndefinedValue to the QJSValue constructor. The undefinedValue() function created a value that was bound to the engine; the QJSValue constructor does not. In order to ensure that we're testing the same behavior as before, I've replaced undefinedValue() calls by toScriptValue(QVariant()) in the autotests. Task-number: QTBUG-23604 Change-Id: Ie9295b7af49c853b5a4a3445da48c325fef8d6b1 Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@nokia.com> Reviewed-by: Simon Hausmann <simon.hausmann@nokia.com>
Diffstat (limited to 'doc/src/snippets/qtquick1/qtbinding/functions-cpp')
0 files changed, 0 insertions, 0 deletions