Qt 6

@Axel-Spoerl said in Build error on qt 6.8: gcc --version it say: gcc (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7) Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Oops! That was right under my nose, but I still managed to miss it. Many thanks, good sir!

running into this issue years later... for me the line find_package(Qt6 QUIET COMPONENTS Core Gui Widgets Multimedia MultimediaWidgets) will NOT populate the version numbers, only repeating with find_package(QT NAMES Qt6) will finally do.

Thank you very much.

Hi, You realize that using all this static stuff is a really good start to a pretty nightmarish maintenance and debugging experience ?

@JonB Yea, I thought writing a dock/taskbar "Waybar replacement" might be a fun weekend project and a chance to get back into C++ and learn Qt. I never imagined this rabbit hole. Anyway, I guess Wayland is still [relatively?] new and hopefully there will be solutions for these use cases as more major distros go Wayland native. It does give me respect for those implementing entire desktop environments such as KDE Plasma on Wayland since it's now clear all the fire hoops they have to jump through to get this stuff working.

@SandSnip3r said in Qt Graphs. Building 2d plot using c++ only.: Isn't the Graphs moved out of technical preview as of 6.8? Should be but as you can see from OPs question QGraphsView, the C++ API to access the QML backend is mentioned in the documentation but not implemented nor it has it's own documentation page... the links lead to nowhere... :( Maybe use the QML interface for now and handle it like any other hybrid QML/C++ app QGraphs should be 2D and 3D + C++ and QML... but not everything seem to work right now.

@mrkprdo Sorry, my bad. I fixed it.

@hdugzx I never used Design Studio, but there should be a menu like "View" or "Windows". Look in "..." in the top-right corner. You also can check the settings. In QtCreator you can disable/enable menu by pressing Ctrl-Alt-m - maybe it also works in Design Studio.

The documentation is quite clear: by default this property is false. There's no reason to pre-fill the background if you are going to fully paint it anyway.

@Shankarlinga-M thanks for your input! The use case is basically a container class, with - almost only -, readOnly access from outside. It will be read from user provided files during runtime and exist until a new set is read or the program is closed. The objects are created and "stored" in a List/Vector to be passed to where they are need to be read. So the list should per design choice be immutable. And I would like to enforce it. The default move assignment operator is deleted due to const members, so thats out too. Looks so far, as if the cleanest way would be using std::vector. Not sure how much refactor/extra work that will be :(

@jsulm Ok, thank you!

@dan1973 said in Qt6 installation: How to resolve this? By doing what the error message suggests you to do: "You can select a different mirror for opensource metadata and downloads. The mirror can be set from terminal using option --mirror. Available mirrors can be found from: https://download.qt.io/online/qtsdkrepository/windows_x86/root/qt/Updates.xml.mirrorlist" Also see here: https://wiki.qt.io/Online_Installer_4.x

I am able to create a QT application that uses USB camera. This was my solution.

This was the solution, to set currentRow() (provided there is any groove data): if((ui->grooveList->currentRow() < 0) && (ui->grooveList->count() > 0)){ ui->grooveList->setCurrentRow(0); }

From here: https://doc.qt.io/qt-6/qtquickcontrols-changes-qt6.html Qt Quick Controls 1 was deprecated in Qt 5.11 and is removed from Qt 6.0. Use Qt Quick Controls (previously known as Qt Quick Controls 2) instead. For more information, refer to the Qt 5.15: Qt Quick Controls vs Qt Quick Controls 1 topic in the Qt 5 documentation. I guess you need Qt Quick Controls 2 and qtquickcontrols2-qmlplugins

Hey, as our docs state: "Users are responsible for managing the unique RPC handlers returned by the Client interface", the RPC object has to be alive to continue any processing. You don't need to connect to finish but it's highly recommended since you don't know when the time for deletion would be.