In this video, we discuss the basics of model/view programming with Qt/QML. How do we expose a set of data (a list, a table, etc.) from the business logic to C++? How much flexibility do we have before the data actually reaches QML?

In this module we'll use the knowledge that we gained in module 7, QObject, signals, slots, properties, variants, in order to make C++ and QML talk to each other. In this first video, we are going to show how we can export objects of value classes (numbers, strings, etc.) from C++ to QML.

This video shows how to export QObject subclasses to QML. While similar to the previous video, QObjects aren't value classes and add features like properties, signals, and slots via the meta-object system. We get all these features when exporting QObjects to QML!

When QObjects in C++ are exposed to QML, who manages their lifetime? Can QML's garbage collector reclaim them if they're still needed in C++? What happens if C++ doesn't delete them, expecting QML to handle it? This video explores object ownership between C++ and QML.

This video discusses how to create GUI elements in C++, and make them available to QML. It's just as simple as creating non-GUI elements, with a very small twist.

Previous videos showed exporting individual C++ objects to QML. This video covers something related but different: exposing C++ classes to QML so QML can create instances. We'll start with non-GUI classes; the next video will cover GUI classes.

Any non-trivial Qt application uses the model/view/controller framework, a design pattern separating data management from UI. This video focuses on the "model" aspect that interacts directly with data. Models are central to Qt across all UI stacks (Widgets, Quick, remote objects). While custom views are rare, developing custom models is very typical.

It can visualize the stack of models for you, but there is one thing you better remember in your code --watch this video to find out what it is! :)

Sometimes views or delegates need to ask questions of the source model at the bottom of a proxy model stack. While the previous video showed using custom roles for cell-specific data, this video demonstrates a better approach for non-cell-related data: traversing proxy models yourself to reach the actual source model.

Got a stack of proxy models where there is a subtle bug somewhere in there? No worries --GammaRay to the rescue! It can visualize the stack of models for you, but there is one thing you better remember in your code --watch this video to find out what it is!

Remember discussing QML properties 25 videos ago? Qt allows you to define properties in C++ for QObject subclasses by describing their type, name, and read/write methods. This final module video covers the Qt Property System, its usage, and how it fits the bigger picture. Bonus: how QVariant relates to the property system.

QVariant is a cornerstone Qt class used in the property system, model/view, and C++/QML data exchange. It's a type-erased container similar to std::any, storing objects of almost any type while remembering the stored type. This video demonstrates how QVariant works in practice.

"unresolved external symbol 'public: virtual struct QMetaObject ...'" - a mysterious linker error that sometimes occurs when working with QObjects and signals/slots. This video explains what causes it, how to solve it with just one click, and what happens behind the scenes where the build system meets signals and slots.