Qt World Summit: Register Today!

Where is the "QML Screen" element documentation ?

  • Hi to all.

    In the local documentation on Qt-Quick and QML found in the Qt Creator package 2.2.1 is explained the Screen QML component. There are only few words about the properties and methods but this element is notified.

    I see that the same element seems undocumented in the new Doc area: i used the same words I searched on the local Qt-Creator documentation "QML Screen Element" to see about it but nothing is found. Is there a lack of documentation or there is some reason so this component is not documented ?

  • Update:

    Found notice on the Screen component. I interpret it as a lack in the documentation. The QML Screen Element is part of the new set of Qt Quick components recently released. It is tru that are experimental but following the link in the Qt labs you go to the new developer documentation area so why don't add links to the rest of the documentation ?
    This is not so clear and not intuitive: people expect that Qt-Quick components are objects to build UI - as described in most of the posts relative to this useful update - The QML Screen Element is part of them and I have found no links in the documentation. In the Qt elements page maybe useful for example a bottom secion with womething like "Experimental components" or "new released components" I think it maybe sufficient to invite the developers to investigate in-depth.

    In the actual Qt-Creator local documentation the QML Screen Element is mentioned without any reference to the fact that it is part of the Qt-Qtuick new tools components that should be imported in the user space.
    The example reports:

    @function lockToLandscape() {
    screen.allowedOrientation = Screen.Landscape

    ("here":http://doc.qt.nokia.com/qt-components-symbian-1.0/qml-screen.html is the link)

    Only if the user reach this page from the main Qt-Quick documentation is aware that to use this component he ned to import them on top of the QML document.

    For all the other compnents I think this can be obvious because are what we can expect: UI components accessible ipmorting the component itself.

Log in to reply