We're happy to announce the release of the Qt Extension Pack 1.2.0 for Visual Studio Code! This release cooked for a bit as pre-release 1.1.0 on the marketplace and has now been promoted to a proper release. Take a look at what's new in our new release.
Usage of custom Qt installations
In the first release, using Qt installations that the Qt Online Installer didn't provide was impossible. You can now add any Qt installation that you installed from a package manager or that you built from sources:
- Go to Command Palette, and select Qt: Register Qt (qtpaths or qmake).
- Select the
qmakeorqtpathsexecutable, and then select Select.
The command creates a CMake kit for the selected Qt installation.
Qt that's been installed with vcpkg in classic mode is automatically detected as well.
Always the latest QML language server
The QML language server enhances the developer experience for QML projects. The 1.2.0 release of our VS Code extension offers to automatically download the latest and greatest QML language server executable from our servers.
This way, you can benefit from the latest improvements of the QML language server without waiting for the next Qt release.
Other project news
GitHub setup
Since GitHub is the natural habitat of VS Code extensions, moving the project there was a logical step. If the Qt project's Gerrit setup was the only obstacle stopping you from contributing, you're out of excuses.
The repository is now hosted at https://github.com/qt-labs/vscodeext
Telemetry
We're now using the telemetry API built into VS Code to learn how our extensions are used. This will hopefully provide some insight into which areas are more important than others and where improvements are most helpful. We don't collect sensitive data and respect the global telemetry setting of VS Code.
If you encounter any bugs or usability issues, please report them at https://bugreports.qt.io/ under the VS Code Extension (VSCODEEXT) project.
Commenting for this post has ended.
The version available on the store is still showing as 1.0.2
OK, I have to admit, this is confusing. The extension pack didn't receive a version update since nothing changed there. But the extensions it pulls in have the new version, e.g. https://marketplace.visualstudio.com/items?itemName=TheQtCompany.qt-cppWe should update the extension packs, too, in the future to avoid this.
Alright, thanks for pointing out 😅
Ah yeah, that makes sense. Probably doesn't help that the web page for the extension pack doesn't seem to show the extensions it includes (or their version numbers); but that is a VS Code issue not Qt's. :)
Thanks for the update. Can't wait for the qml debugger!
We hope to be able to provide QML debugging support in the next version.
The store still shows 1.0.2 instead of 1.2.0
See my comment above. The extension pack still sports the old version number.
Android kits are also listed but they don't seem to be working? Configure fails looking at (predefined?) /opt/ paths as far as I can see. Didn't see anything about Android on the backlog so not sure if that means it's supported or not planned yet at all? Nice work otherwise!
If you haven't already - could you please file a bug report about this at bugreports.qt.io?