r/QtFramework

I'm looking into creating a CAD-like application (though extremely domain-specific). Is it possible to use some GUI framework like Qt or Gtk and host a view running the Bevy engine for visualization and manipulation? Or would I have to create all the UI in Bevy?

I'm trying to load a PDF in a Qt Widget application using threading. Irrespective of what I do, it fails to load the PDF. I tried creating a concurrent thread, made a new QPdfDocument, loaded a PDF into the entity and then moved it to the main thread before returning the pointer. It still doesn't work! Here is an MWE (I know that the PDF loading in this example is synchronous, but even this fails to work - forget about loading the PDF asynchronously):

  QFuture<QPdfDocument*> future = QtConcurrent::run([](){
    QPdfDocument* loadDoc = new QPdfDocument();
    loadDoc->load(ProjectSettings::instance().pdfPath);
    loadDoc->moveToThread(QApplication::instance()->thread());
    return loadDoc;
  });

  m_document = future.result();

Is there any reason to use a QML GridView over a GridLayout with a Repeater when all items are always displayed on screen and scrolling is disabled?

I ask because I'm finding GridView's concept of fixed cellwidth/height restrictive and I'm able to achieve what I need with a GridLayout + Repeater. Just wanted to make sure I'm not breaking some golden QML rule.

Hey everyone, I am seeking a little bit of advice from some more experienced Qt developers. For context, I have been using PySide6 to develop a couple of applications over the past 3 or so months, so I am relatively new to Qt development and the Qt Ecosystem in general. Recently, I've noticed a bit of an issue with the maintainability of the Signals in Qt.

In general, I have been structuring my projects in a relatively strict tree. I have a root "MainApplication" class that owns all UI widget classes, as well as any additional classes needed to do back end work. (I've been creating GUI applications for hardware, so usually back-end work looks like writing serial data of some sort.) My UI widgets then usually look like a tree where I have some sort of view/page that does a specific thing, and then I have additional nested widgets depending on the task I am trying to accomplish. Usually, I will define each individual Widget in it's own file, so a Serial terminal widget might be defined in a "serial_terminal.py" file.

The main issue I've been running into is when I have a deeply nested widget that exists far into the project's tree structure, and I need it to effect something on the back-end. Lets say I have an "Emergency Stop" button that's nested 5 widgets deep from my "MainApplication" class. That emergency stop button will need to emit a signal to my "HardwareManager" class to make something happen. To accomplish this, what I have been doing is having whatever classes own the button to emit that signal all the way up the tree, so that the MainApplication can finally connect it to the HardwareManager slot. This means that whenever I add a new button to one file, I'll have to edit up to 5 (or more) additional files just to add its intended functionality.

This problem seems very similar to React's "Prop drilling" issue, which is what Redux and other state managers try to solve. However, after a little bit of digging, I didn't seem to find much in the Qt ecosystem that aims to solve this issue, or even much discussion of this issue in the first place.

So my question is: What's the solution? Is the problem in the way in which I choose to structure my applications? Are there state managers out there that I missed? Do you just grit your teeth and accept the inconvenience? I would love to hear the thoughts of some more experience Qt developers!

Where is Qt used the most today in terms of countries, industries, and companies?

I am curious where the demand for Qt C++ developers is strongest ?

Hey, I'm looking at a customer service job from the past three years and now I want to switch my career and get into software development. I have tried to learn web development but due to race in competition and AI it seems like going there would be a pretty tough job. And everybody starts from there. So that is the reason I started learning C++ And now I want to get into QT development. I have no idea what I am going to do. Please help me out with the resources or any suggestion. It will be really appreciated. Please keep in mind that I want to Land a job in this field.

Hi there! Has anyone successfully used devcontainer support in Qt Creator?

I’m trying it with v20, but I can’t get it to run. It appears in my project tree, and the Docker image has everything it needs. The same image also works when configured directly as a device. However, the devcontainer stays red and isn't available in Kits. I think I'm missing a step but I don't know which one.

Does anyone have a working example?

I’m on Debian 13, using a Debian 13 Docker image, in case that matters.

For a document editor that supports Japanese text it should be able to write vertically. Also, if I'm not wrong, there are some characters that are different when written vertically. Is there an easy way to do all that in a rich text editor widget?

I assume that those are the main problems. The character writing itself and to show them I guess it's already solved by other things, like html format, etc. And I don't know if I have to worry about anything else about that

Are there tutorials or walkthroughs for programming shaders on Qt 6 that you can recommend? The first thing I want to do is draw QSGGeometry lines with varying line thicknesses but I’m finding it difficult to get started.

I'm quite a beginner but quite interested in the visual layout of applications in QT Creator. (C++, without QML) On the other hand I start to find myself creating custom widgets. And I cannot always see a full visual preview.

What's a good balance between "visual editing" and custom Code?

The goal is to make day-to-day 3D scene editing in QML feel closer to a dedicated game/editor workflow while staying compatible with Qt Design Studio-style .qmlproject projects. In this walkthrough:

• importing 3D assets into a Qt Quick3D scene
• selecting objects directly in the viewport and outliner
• moving, rotating, and scaling scene nodes with editor gizmos
• working with imported model animations and timelines
• editing shader/material graphs
• editing particle graphs
• previewing changes directly in the scene

XyrillForge is currently a proof of concept / work in progress. The focus is source-compatible, WYSIWYG 3D editing for QML scenes, with source files remaining the authority and the runtime scene acting as a live preview.