Sérgio Martins
16 results
Qt Test is a framework designed for unit testing applications and libraries built with Qt. It provides all the standard features commonly found in unit testing frameworks, making it easier to write unit tests for Qt-based projects. We're happy to introduce the QtTest Runner - a Visual Studio Code extension for running Qt Tests via […]
Supercharging VS Code with C++ Extensions
9 November 2023
In a previous blog we demonstrated the most straightforward method to optimize Visual Studio Code for a Qt / C++ environment: simply let the tools do all the work! The example GitHub project we discussed automatically installs both the Microsoft C/C++ and clangd extensions into VS Code. You might wonder why you need both C++ […]
Our colleague Alessandro Ambrosano created a series of blogs (parts 1, 2, and 3) that explain how to get Visual Studio Code configured for Qt development. In that series, Alessandro covers all the details you need to get your VS Code environment configured exactly the way you want it. But there’s a lot there to […]
CMake 3.19 was officially released a couple of months ago, and one of the biggest – and most exciting – new features is the addition of presets. What are presets, you might ask, and why should we be excited about them? Presets are a bunch of pre-set CMake options that enable developers to ensure that […]
KDDockWidgets v1.1 is now available! Although I just wrote about v1.0 last month, the 1.1 release still managed to get a few big features. Here's the ChangeLog: Auto-hide/SideBar support This was much awaited and probably the last essential feature that was missing. You can now set a dock widget to auto-hide to a side bar. […]
The KDDockWidgets 1.0 release is now available! What is KDDockWidgets? KDDockWidgets is an advanced docking system for Qt, with features that are not available in QDockWidget. See our first blog post, for a quick introduction and the motivation for a new docking framework. What's new in 1.0? We've come a long way since the initial […]
KDDockWidgets is an effort by KDAB to provide an advanced docking system for Qt. Throughout the years KDAB has contributed and funded QDockWidget development. Sadly, this wasn't without pain: each change took many days to implement and an equal amount of time to fix regressions. QDockWidgetmixes GUI code with logic/state in a spaghetti manner, making […]
Clazy 1.5 is now available. This is a small release, mainly focused on bug fixing. Clazy is a clang compiler plugin which emits warnings related to Qt best practices. We'll be showing Clazy at Embedded World, Nuremberg, Feb 26-28, where we are a main Qt partner. You can read more about it in our previous […]
Enter the wonderful world of tools for which the announcement blog takes more time to write than the tool itself. qsslint is a small command-line utility for verifying the syntax of your Qt stylesheet files (*.qss). It's much like KDAB's previous linter contribution, qmllint. It simply returns 0 if the stylesheet is valid, and non-zero […]
Clazy 1.4 has been released and brings 10 new checks. Clazy is a clang compiler plugin which emits warnings related to Qt best practices. We'll be showing Clazy at Qt World Summit in Boston, Oct 29-30, where we are a main Sponsor. You can read more about it in our previous blog posts: How to […]
Nailing 13 signal and slot mistakes with clazy 1.3
Create better Qt code by automatically uncovering easy-to-miss errors
Today I want to share 13 mistakes regarding signals, slots and connect statements and how to find them at compile time with clazy, our open-source static-analyzer for Qt. Clazy is a compiler plugin which generates warnings related to Qt. You can read more about it in our previous blog posts: How to use static analysis […]
Clazy is a clang plugin which extends the compiler with over 50 warnings related to Qt best practices ranging from unneeded memory allocations to API misuse. It's an opensource project spawned by KDAB's R&D efforts for better C++ tooling. Today, we're proud to announce a Clazy Web UI to view all warnings emitted by Clazy, […]
In the previous episode we presented how to uncover 32 Qt best practices at compile time with clazy. Today it's time to show 5 more and other new goodies present in the freshly released clazy v1.2. New checks 1. connect-not-normalized Warns when the content of SIGNAL(), SLOT(), Q_ARG() and Q_RETURN_ARG() is not normalized. Using normalized […]
Uncovering 32 Qt best practices at compile time with clazy
Generating compile-time warnings and automatic refactoring for Qt best practices
In a previous blog post we introduced clazy, a clang plugin which makes the compiler understand Qt semantics, allowing you to get compile-time warnings about Qt best practices ranging from unneeded memory allocations to misuse of API, including fix-its for automatic refactoring. Today we'll do a round-up and present the checks related to connect statements, […]
It's usually said "only improve performance where a profiler tells you to". I don't completely agree. Take a big C++ library like Qt: can you profile all classes and all code paths ? It would take a couple of years to accomplish and analyse the results. It's expensive: It usually only happens if the speed-up […]
One type of bug I see very often comes down to syntax errors in QML and JavaScript files. Most of the time these errors are simple typos; however, they creep in, go unnoticed by continuous integration and sometimes reach production -- especially on delayed loaded components. I like fixing bugs, but what I love even […]