The Lounge

@Pl45m4 My understand is that this applies to anyone distributing software in the EU. It doesn't matter if you/your company is from the EU, but only if some of your clients/users are from the EU. The source code itself is not a product, yet. This means you can publish source code on GitHub without following the CRA. I assume that if you also provide compiled binaries on GitHub you'll fall under the open-source rules of the CRA. Honestly, I have skipped the articles about open source, but I have seen that there are certain rules to be followed for maintainers of open source projects. I guess we could start a discussion if GitHub itself is the distributor of the compiled binaries inside the EU and has to conform to the rules of the CRA. On the other hand, they might just claim that they provide a service and each individual publisher of binaries is responsible for the CRA. I would expect GitHub to either change their terms accordingly or maybe provide an option not to publish the binaries inside the EU.

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.

@Thank-You, login.qt.io/change_email now exists.

@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 :)

Closing as duplicate of https://forum.qt.io/post/809400

@linuxguy123 they will start to once they realize the code blocks is not checked.

Just use proxy: quterussia.ru/download/

@berry36 Don't worry too much. Toxic and now banned ex-user (= threadstarter) getting her own medicine ;-) The original post was edited multiple times... so her initial message was something completely different that got replaced by her with some random question afterwards

@SGaist Ok, thanks.

Hi and welcome to devnet, I don't have an answer to that issue. Sorry for that. But what exactly would you need ? The open source version might already cover your requirements.

@markleo So you mean "projects" (or software) maintained and published by Qt? Or what "other projects"? If so, you forgot to mention Qt's C++ core framework as "Qt for Python" are bindings for Python based on the C++ Qt Framework. The PySide Python wrapper for Qt is developed by the Qt Group, however other implementations such as PyQt (by Riverbank) exist. If you are talking about things not developed by Qt... there are millions of side projects that evolve around Qt. For this check GitHub or similar platforms.