<![CDATA[Update QtQuickControls - rename all imports ?]]>what's the recommended way to deal with new versions,
per example using Qt 5.7
import QtQuick.Controls 2.0

and updating to Qt 5.8

should I rename all imports from
import QtQuick.Controls 2.0 to import QtQuick.Controls 2.1 ?

]]>https://forum.qt.io/topic/76721/update-qtquickcontrols-rename-all-importsRSS for NodeTue, 21 Apr 2026 14:24:24 GMTTue, 28 Feb 2017 19:31:47 GMT60<![CDATA[Reply to Update QtQuickControls - rename all imports ? on Tue, 28 Feb 2017 21:55:22 GMT]]>@jpnurmi yep - sounds like a nice feature to do it without a version and get the latest.

think I'll do a rename to keep versions consistent and to be sure all qml files 'know' the newest properties

]]>https://forum.qt.io/post/379042https://forum.qt.io/post/379042Tue, 28 Feb 2017 21:55:22 GMT<![CDATA[Reply to Update QtQuickControls - rename all imports ? on Tue, 28 Feb 2017 21:39:10 GMT]]>Sounds like a nice feature request... Doesn't it ? ;)

]]>https://forum.qt.io/post/379036https://forum.qt.io/post/379036Tue, 28 Feb 2017 21:39:10 GMT<![CDATA[Reply to Update QtQuickControls - rename all imports ? on Tue, 28 Feb 2017 21:36:40 GMT]]>Technically, it's not necessary to touch the import versions except in those files where you want to use new types or properties that are not available in the older version. It's up to you whether you prefer to apply minimal changes and that way create a mixture of import versions, or if you want to bump all the import versions to keep them consistent across the code base.

Considering the hard to remember QML versions, it's a real shame that it's mandatory to specify the minor version at all. It would be nice to be able to optionally specify just the major version, or no version at all, and just get the latest, right? :)

]]>https://forum.qt.io/post/379033https://forum.qt.io/post/379033Tue, 28 Feb 2017 21:36:40 GMT