General and Desktop

@SimonSchroeder said in Where are the .ui files?: I am so vocal about it because I was taught to use pointers and new everywhere when I started with C++. Turns out that this was the source of most bugs. So, using stack variables almost everywhere (except for Qt's objects with parents assigned) helps to prevent a lot of bugs. (There are other reasons to use pointers related to OOP and polymorphism, but even then there are fewer cases than I was taught initially.) True. This correlates also with my experience. @Pl45m4 said in Where are the .ui files?: Have seen beginners creating everything, Qt and non-Qt related stuff, on the heap regardless... that could need some optimization :) Could be "bad" teachers, wrong guides or courses... or just the wrong assumptions that it needs to be done this way. People have heard "C++ is hard", "C++ is complicated", "Lots of bad black memory/pointer magic you can do"... which is kinda accurate... so they take the sledgehammer to crack a nut :D And maybe they get "inpired" by other OOP languages like Java, where you don't have to manage your memory yourself and new'ing something does not come with any drawback, therefore it's most used.

I didn't expect this (but admit that I should have checked it earlier...) Using 6.9.0: When selecting "winrt" as engine it output the format error, but using "sapi" it works. Using "winrt" the Application Output shows "QAudioSink::start: QAudioFormat not supported by QAudioDevice" Still don't know how to fix the problem for winrt, but it's a step forward. Also, the application needs to work for alle engines the end user select in order to support all locales and voices. It would be interesting to know if this only applies to my setup or if anyone else using Windows 11 and Qt 6.9.1 experience the same issue with this code I still can't figure out how to set the format of the default output

Hi @SimonSchroeder Nope. I build the projects in Release mode.

It looks like that doc page was updated. A requirement line encompasses all the Android requirements, and it states that QC can download these for you.

Thanks @Ben-Campbell-Wallis and @JonB for the reply.

@thunder What's your question?

You should not change the way you write code based on a linter if the linter is wrong. However, widget should have a parent (maybe that happens when it is added to a layout). If you are using a linter, you shouldn't just turn it off entirely. So, the option that you have is to turn specific linting options off on a per line basis (https://stackoverflow.com/questions/37950439/inline-way-to-disable-clang-tidy-checks): Use NOLINT(...) on specific lines or NOLINTBEGIN(...)/NOLINTEND(...) on the whole section of code creating widgets and layouts. Make sure to just disable that one specific warning.

Hi, Using multiple views on top of the same model is one of the core feature of the model view paradigm. You have one single source of data and present it through different (or similar) means to the user.

It is a problem with the installer's binaries they were build on Ubunto with a different libc or libstdc++ library than on Raspberry. https://bugreports.qt.io/browse/QTBUG-137145 You can build it from the sources, then it works. Install required packages sudo apt install cmake libfontconfig1-dev libdbus-1-dev libfreetype6-dev libicu-dev libinput-dev libxkbcommon-dev libsqlite3-dev libssl-dev libpng-dev libjpeg-dev libglib2.0-dev libgles2-mesa-dev libgbm-dev libdrm-dev libvulkan-dev vulkan-tools Install wayland libs sudo apt install libwayland-dev libwayland-egl1-mesa libwayland-server0 Download and extract https://download.qt.io/official_releases/qt/6.8/6.8.3/submodules/qtbase-everywhere-src-6.8.3.tar.xz, tar -xf qtbase-everywhere-src-6.8.3.tar.xz Switch to the directory where the file is extracted, make a directory for the build inside, switch into the build directory cd /path/to/qtbase-extract, mkdir ./build, cd ./build Build cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/home/raspifm/Qt/6.8.3-aarch64 -DQT_FEATURE_opengles2=ON -DQT_FEATURE_opengles3=ON -DQT_FEATURE_kms=ON -DQT_AVOID_CMAKE_ARCHIVING_API=ON .. cmake --build . --parallel 4 Install cmake --install . Build modules, e.g.: qtsvg, qtimageformats, qtwayland Download and extract https://download.qt.io/official_releases/qt/6.8/6.8.3/submodules/qt....tar.xz tar -xf qt....tar.xz Switch to the directory where the file is extracted, make a directory for the build inside, switch into the build directory cd /path/to/qt...-extract, mkdir ./build, cd ./build Build /home/raspifm/Qt/6.8.3-aarch64/bin/qt-configure-module .., then cmake --build . --parallel 4 Install cmake --install .

That solved it. I'm not sure what happened, but something got messed up my build dir.

@JonB, that's what I was looking for! Thanks.

Hi and welcome to devnet, Does it happen with only a single file or are they all affected ? It there somewhere a sample file that could be used to test this issue ? Which OS are you running your application on ?

That's how I understood the code.

@rcx11 it uses a similar approach to gRPC/QtRemoteObjects in that the files that are compiled are generated using calls to the generators via cmake. I checked Qt6.10.0 on windows 11 and indeed, until you configure the file cannot be found: The file that generated (for reference of others reading this thread): [image: 8bfbacc8-18a1-419d-9f48-7757554d7203.png] I'd recommend marking as resolved with @Paul-Colby 's response.

Hello, is there any update for this issue? I'm also facing the problem that the QEnums properties are not loaded by QtDesigner

It works fine for me with Qt6.9.1 with the windows11 style: int main(int argc, char *argv[]) { QApplication app(argc, argv); QTableWidget tw; tw.setRowCount(5); tw.setColumnCount(1); auto item = new QTableWidgetItem("Item"); tw.setItem(0, 0, item); QTimer::singleShot(2000, &tw, [&]() { tw.item(0, 0)->setCheckState(Qt::Checked); }); tw.show(); return app.exec(); } Please provide a minimal, compilable example of your problem.

@SuhasKrishanamurthy hi, Since you marked your thread as solved, can you share what you did / change to fix the situation ? It might help other people.