The Qt.application documentation says:
In addition to examining properties like name, width, height, etc., the array elements can also be assigned to the screen property of Window items, thus serving as an alternative to the C++ side's QWindow::setScreen().
...which sort of works, but might not be the expected/desired behavior (ie assign works, but binding doesn't)
For example, this fails:
... with ""ApplicationWindow.screen" is not available due to component versioning.", but
I know managing the lifecycle of attached properties like Screen can be tricky, but if this is the intended behavior, the documentation needs to be more clear on the recommended ways of how to use it.
|For Gerrit Dashboard: QTBUG-60893|
|194939,3||ApplicationWindow: fix access to revisioned members in base classes||5.9||qt/qtquickcontrols2||Status: MERGED||+2||0|