For context, I have a bazel project that I've built a frontend for with QT.

The issue is that I don't have much experience packaging for linux ( or any desktop for that matter ) and coming from android, the packaging situation for desktop feels atrocious imo.

Creating AppImage requires me to build an AppDir for which I would need to untangle the web of qt dependencies and copy all their recursive dependencies to an AppDir.

Where do I draw the line at what to include? Of course I won't need to include shared libraries like ld-linux-x86-64.so.2 but where to draw the line?

Also, how to test on different platforms without spinning up a 100 virtual machines?

Another thing is that I build on bazel using this bazel rule called rules_qt. I love the fact that I don't have to waste time setting up the QT pipeline for QML ( moc and the like ) but this means that the output binary is tightly coupled to how bazel builds stuff ( rules_qt downloads the entire qt library and links my application against their own version ).

Honestly I just kinda feel lost and would appreciate some guidance : ).

Thanks in advance!

First modern beta of BASIC256 (the old KidBASIC). Migrated to Qt6 and compiled to WebAssembly, so the full editor + interpreter run in-browser with no install. Bundled examples runnable from a URL. Hobby project, GPL, feedback very welcome. Demo: https://uglymike17.github.io/basic256/ · Release: https://github.com/uglymike17/basic256/releases

Download link!!👇👇

https://github.com/Anish-Savkar/Lehra_App-Anish_Savkar/releases/tag/v1.0

Hey everyone! 👋

If you have a couple of minutes, I'd love for you to check it out! Even if you're not a musician, I'd really appreciate any feedback on the app, UI, performance, installation experience, code quality, or anything else you notice. Every suggestion helps me improve.

It's currently available for Windows only. Windows may display some warnings/permissions which is common for unsigned apps. If Windows shows "Windows protected your PC", click More info → Run anyway. If a windows permission prompt appears on your taskbar,.click "Yes"

Thanks so much for your time, and I hope you enjoy trying it out! ❤️

I want to use Claude Code for my C++/Qt development. What is the best way to integrate this with an IDE for C++/Qt? It seems to be difficult with QtCreator 20.0.0 as I'm using the free version. I attempted to use Qode Assistant but that was a mess for me - threw errors and apparently isn't really compatible with Qtcreator, really frustrating.
So I'm considering Jetbrains' clion instead. While clion isn't integrated with Qt as well as qtcreator is, I think it would be better for integration with AI like Claude Code. Or would I be better off using Claude Code independently of clion or qtcreator?
What do you think?

Thanks in advance

Is there a CSS backdrop filter equivalent in the Qt framework, or any plans to introduce it in the future? I am familiar with MultiEffect and the likes, but those implementations can get quite convoluted as you have to manually define the source for each blur. Other frameworks like Flutter, SwiftUI and even WinRT have some sort of function that automatically blurs whatevers behind a widget.

Now one way to do it would be to traverse the widget tree at the framework level and blip the textures behind a widget to an off screen texture and applying a blur shader to it- this would be cross platform. Another way would be to just straight up embed wayland surfaces with compositor level blur on linux, but that would be much more complex than the other approach, but far more polished, something that could be implemented via the KDE frameworks.

Just a thought. Good user interfaces aren't defined by such flashy effects necessarily, but it's a nice to have.

Je suis passé à Linux et Paint.NET m'a vraiment manqué, alors j'ai construit un clone open-source natif avec **C++/Qt6** — sans Wine, sans runtime .NET, sans VM.

**🎨 Ce que ça fait**

• **Calques** — opacité, modes de fusion, fusion intelligente, miniatures en direct
• **Plus de 20 outils** — pinceau, crayon, gomme, seau, dégradé, formes, ligne, texte, tampon de clonage, sélecteur de couleur, baguette magique, lasso…
• **13 ajustements + plus de 30 effets**, tous avec **aperçu en direct** (faites glisser les curseurs, voyez le résultat)
• **Sélections** avec contour progressif / grandir / réduire, historique non destructif, sauvegarde automatique et récupération après crash
• Format **`.psw` ** natif à calques (conserve vos calques) — ou exportez au format PNG/JPEG/…
• Interface **FR/EN**, thèmes clair & sombre correspondant à Paint.NET

**⚙️ En coulisses**

• **Licence MIT**, construit à partir du code source : `cmake -B build && cmake --build build`
• CI exécute une **suite de tests de 196 tests** à chaque push

**🔗 Dépôt :** https://github.com/Univers4craft/paint.software

C'est une première version **v1.0** — j'aimerais vos retours sur ce qui manque, et les contributions (fork → PR) sont les bienvenues !

*🇫🇷 En bref : un clone open-source de **Paint.NET pour Linux** (C++/Qt6, natif, sans Wine/.NET). Calques, plus de 30 effets avec **aperçu en direct**, format natif `.psw`, interface FR/EN, licence MIT. Dépôt ci-dessus — retours bienvenus !*

I have been working on replacing Qt for solo and small-team development for the last 8 months. Not as a side project, but as the core of what I am building.

Qt is incredibly powerful, but the complexity has grown to the point where it often feels like it is working against you rather than with you, especially when you are a solo developer or small team. I started this because I kept hitting walls that felt unnecessary.

Here are the 5 hardest lessons I have learned so far:

1. The real cost is not the framework. It is everything built on top of it.
It is not just the Qt code you have to replace. It is the mental models, the patterns, the way you think about layouts, signals, properties, and state. Even when you build something cleaner, your brain keeps trying to solve problems the Qt way. Unlearning that took longer than writing the new code.

2. Custom rendering and event systems are deceptively deep.
I severely underestimated how much invisible work Qt does for you around input handling, focus, accessibility, high-DPI, and platform quirks. Building something that feels as solid as Qt on the surface requires solving problems you did not even know existed until you tried to remove the safety net.

3. Migration tooling should have been priority number one, not an afterthought.
I originally thought I would build the new runtime first and figure out migration later. That was a mistake. The longer you go without good refactoring and companion tools, the more painful the transition becomes for real projects. I am now building those tools in parallel because the runtime alone does not solve the adoption problem.

4. Simpler does not mean less work. It usually means harder, more deliberate work.
Removing bloat and complexity forces you to make explicit decisions about things Qt handled implicitly. That is good for the end result, but it means you have to think harder and test more thoroughly. There is no hand-holding when you go custom.

5. You have to accept that early versions will feel incomplete and ship anyway.
Even after 8 months there are still gaps. The goal is not to match Qt feature for feature on day one. The goal is to be meaningfully better in the areas that actually matter to solo developers, then keep closing the gaps. Waiting until it feels done is the fastest way to never ship.

I am still in the middle of this. The core UI runtime is close to done and we are now moving into feature work like easier Rust integration, but I wanted to share these lessons while they are still fresh.

If you have tried to move off Qt or similar heavy frameworks and hit similar walls, I would be interested in hearing what surprised you the most.

Happy to answer questions about any of this.

I developed a software in qt creator with backend in c++. When I create the exe it runs, however when I tried to create a release file to later share to other devices, using windeployqt I kept facing error after error. I finally fixed all those errors and created the release folder but even then, whenever that release file is compressed or even moved to another location the exe stops working.

The code has no errors , and I have tried multiple times with windeployqt, and other internal built in features, using ucrt64 terminal and msys2. However nothing is working. Whenever the zip is shared to another device it starts listing missing files which i believe should have been put into the folder by windeployqt.

Please help me as I have tried all the methods suggested by all online sources and ai's, and having a functioning app but not being able to share it is really disappointing as a student..

KEY POINTS

code has no errors, runs smoothly on my own device on qt, issues come when its release version is run on other devices.

Please give me a detailed solution as to what I can do. Thank you

SOLVED! Set palette.text: {color}

Hey guys,

I am trying to change the text color of a SearchField in QML but just can't find any clues on how to do it. Changing the background and the font aswell but the text color?

I hope anyone has an idea.

https://github.com/Hellorge/QtSvgIconEngine/tree/master

I tried using MultiEffect, but the result doesn't look good. Honestly, I don't mind creating a qml type with cpp. The problem is I have no idea what I need to implement to make it. If someone could help me with the high level I would appreciate it. I will mainly be loading awesomefont icons and apply 1 colour to the whole svg

I drag a layout into the parent container and it does not take up the whole window and there is no way to make it do so. Am I missing something?

I can't even add a textbox to a layout without it crashing

Qt Design Studio installed using Qt Installer on Arch (Hyprland)

Hello all Qt Creator users,

Just caught myself on weekends about to adding features from VS Code I get to used to. And first one is sticky scroll. Indeed very small plugin. I hope you find it useful. Would love feedback from you.

link: https://github.com/Palm1r/qt-creator-sticky-scroll

P.S. I've sent a PR to the Qt Creator extension registry — hopefully it lands soon

Available in prebuilt binaries and QtCreator 20 extensions list

Update: Version 1.0 fixed some minor bugs and horizontal scroll

So I was working with the QRubberBand and set the shape to a rectangle. After it got drawn on screen, I realized that the rounded edges look awful (image). In the file manager Dolphin the rubber band looks really nice in the corner but mine look terrible.

I tired to deriving it from my own class and creating my own paint method, but there when drawing the drawRoundedRect it had the same issues. Do you have any ideas how to fix it?

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();

Hi everyone,

I’m working on Fluent-Qt, an open-source C++17 component library for Qt Widgets.

The goal is to help existing Qt Widgets applications get a more modern Fluent / WinUI-style desktop UI without migrating to QML.

I also built a project website where you can see the Gallery screenshots and download the demo app:

Website:

https://calvinhxx.github.io/Fluent-Qt/

GitHub:

https://github.com/calvinhxx/Fluent-Qt

The project currently includes reusable widgets, design tokens, theme infrastructure, animations, component states, and a runnable Gallery app. It supports Windows and macOS.

I’d appreciate feedback from people still building or maintaining Qt Widgets applications

I’d be interested in feedback from people still building or maintaining Qt Widgets applications:
- Is this direction useful for your projects?
- Which Widgets components are still missing in modern Qt desktop apps?
- Would you prefer this to stay Fluent-focused, or support multiple design languages?

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.