The Lounge

Maybe with a custom QGraphicsEffect calling drawSource with a scaled/translated QPainter. Another solution would be to use QWidget::grab() periodically to get a QPixmap of the widget and overlaying that on top of it. For potential future readers looking for the minimap keyword: In Qt Quick it's pretty easy to do so with just a scaled down ShaderEffectSource.

@inam said in decline of Qtforums: licensing has become restrictive The open source license has always basically been the same. And the Qt company has always tried to scare people into buying the commercial license. I'm not sure if anybody is driven away by changes in the commercial licenses. @inam said in decline of Qtforums: and younger developers prefer Flutter, React Native, or web apps This would only be relevant if these technologies are stealing people away from C++. However, C++ is still growing: https://herbsutter.com/2025/12/ . Maybe there is a shift in regular desktop apps away from C++ (I don't know).

For an address verification error during a Qt product purchase, you’ll need to contact Qt support directly. The community forum won’t be able to resolve checkout issues.

CMake can be frustrating, especially when dealing with Windows SDK dependencies across different machines. Its main purpose is to standardize builds and manage cross-platform projects, which helps Qt stay portable in the long run. If portability is key, consider using Qt’s online installer or prebuilt packages to avoid some of the CMake headaches.

@cbum63 Using AI for a Qt GUI can jumpstart your design and save time if you’re new, but it often creates messy layouts and oversized windows. For experienced users, manual design is usually faster and helps you stay sharp. AI is best as a helper, not a replacement.

It's hilarious, when you go to Akismet.com their front page is flaunting that their spam filter is accurate 99.99% of the time. Wow, we must all be the 0.01%

With everything I've read, I'll try to respond to your questions more explicitly. @Cfan said in Questions about CRA regulation(Cyber Resillience Act): If I create an LGPL licensed app and sell it in EU(online sell), does CRA regulation apply to my situation too? The only excemption from the CRA is non-commercial open source software. So, if you want to sell in the EU, your software will fall under the CRA. I am not sure what you mean with an "app under the LPGL". Is all your own code open source as well? Then you "only" need to follow articles 13 and 14. If your own source code is not open somebody has to follow more rules. If you are located inside the EU it'll be you yourself. If you are located outside the EU it will get more complicated. I am not sure what roles are distributed to "manufacturer", "importer", and "distributor". It might be that the app store might have to fulfill some of the duties instead of you yourself. @Cfan said in Questions about CRA regulation(Cyber Resillience Act): If my app does not use networking or internet, does it change something? Yes. There is the category of "important products with digital elements". What makes a product "important" are things like internet connectivity. "Important products" have to fulfill additional obligations. Without any additional knowledge about your actual app I would guess that it is not an "important product". You'll find a list of important products in Annex III.

A TODO.md file in the project directory, with a VS Code markdown plugin.

What update rate is being attempted? What does the general program structure look like?

Thank you for your reply. Your suggestion was the key to solving a problem I had been struggling with for a very long time. You were completely correct. The root cause was a Qt 5 vs. Qt 6 API change. I was trying to use the obsolete QCameraInfo class in my Qt 6 project. As soon as I refactored my code to use QMediaDevices::videoInputs() and the QCameraDevice class, the "file not found" error was resolved. I had spent many hours trying to fix what I thought was a broken installation, so your insight was incredibly helpful. Thank you for sharing your knowledge!

There are a great many who would use it (like my father). However, VB6 has been deprecated by MS since the 1990s, so I cannot envision The Qt Company implementing this.

Just to be sure because some beginners mix QtCreator and Qt: The version of QtCreator usually doesn't matter. You can still use older versions of Qt with a newer QtCreator. There is usually not much reason to use an older version of QtCreator. What you most likely mean is old versions of Qt. The installer uses a filter to show the most relevant versions. In my version of the installer (not sure if it is the most recent one) to the right of the search bar is a drop down saying "Show". In that list you can enable "Archive" to show older unmaintained versions of Qt. However, this history does not go back right to the beginning, but only selected versions of Qt are shown.

@warhawk627 , Thank you! Your suggestion is working perfectly for me!

I use Qt as a cross platform library for desktop applications. That's why I am still using QWidgets and not QML. Also, I do understand the use of QML for larger companies that have separate designers (we don't), but for the common C++ programmer it is not actually necessary. As a C++ programmer I would certainly support being able to use QML widgets right from C++ without actually requiring QML at all). As @Axel-Spoerl already mentioned it is unlikely that QWidgets will be abandoned any time soon. Even if it does happen, I am not to concerned. It would be still possible to continue open source development of a Qt fork. There have been interesting forks in the past (based on Qt 5). Verdigris (https://github.com/woboq/verdigris) tries to get rid of moc (by using macros) and still be ABI compatible with Qt. CopperSpice (https://www.copperspice.com/) takes a slightly different route and tries to use proper C++ code instead of macros. It is not ABI compatible with Qt. Also, they have reimplemented a few things which means it has diverged from Qt and you cannot just compile Qt code using CopperSpice anymore (I believe this worked initially). With the advent of reflection in C++26 (and hopefully more reflection features in C++29 that make it more usable) I do hope to see a change in Qt or something derived from it. This would certainly help us to get rid of the moc for good (without sacrificing any of the beloved syntax).

Presonus Studio One: https://www.presonus.com/pages/studio-one-pro

@L0uisc The simple answer is that Qt must have have hundreds of classes and thousands of methods. You could add useful/utility features forever. There is no deep reason why one is offered but not another, other than popular usage. QInputDialog --- which by the way is not used that often --- is only really a convenience class on top of QDialog. Nothing wrong with your suggestion --- and you can always make those at https://bugreports.qt.io/, or offer to implement it yourself --- just TQtC probably has a million other things to do :)