QML and Qt Quick

You should try with a current version of Qt. IIRC it's 6.10.1 at the time of writing.

Hi and welcome to devnet, You should also add: which version of Qt you are using which OS you are running on if Linux, which distribution, desktop environment and window manager

@helios831 There should not be any flicker. If you'd like us to help you troubleshoot, please show your code that contains the flicker.

Yes but not necessarily 6.10.0

Here I report also the solution: adding the following lines to CMakeLists.txt qt_add_qml_module(MyTheme ... same code as before ... ... ) if (TARGET MyThemeplugin) target_sources(MD3Themeplugin PRIVATE MyThemePlugin.hpp) endif()

@Hruthik-T-M I've reported this to LLVM that they should ship the CMake files needed to consume the libraries, and they closed it as won't do. You can use Qt's LLVM prebuilt libraries at https://download.qt.io/development_releases/prebuilt/libclang/qt/ You get also the MinGW build of LLVM.

My current workaround, lol: onClicked: function(getDate) { if(getDate.getHours() > 0) { myDate = new Date(getDate.getFullYear(), getDate.getMonth(), getDate.getDate() +1); } else { myDate = getDate }

It fix my bug OpacityMask // Actual masked image { id: opacityMask visible: image.source != ""

Hi, There's two things you can do to make that happen: check the bug report system to see if there's already something about this issue (and if not please create a ticket) submit a patch since you already have the solution at hand :-)

Thank you! I got rid of the .qrc file: https://forum.qt.io/topic/145308/qt-6-5-qml-in-qrc-vs-qt_add_qml_module-what-is-better/3 CMakeLists.txt: set_source_files_properties(qml/MyApp/Main.qml PROPERTIES QT_RESOURCE_ALIAS "Main.qml") set_source_files_properties(qml/MyApp/pages/LoginPage.qml PROPERTIES QT_RESOURCE_ALIAS "pages/LoginPage.qml") qt_add_qml_module(appultiphone URI MyApp VERSION 1.0 RESOURCE_PREFIX "/" QML_FILES qml/MyApp/Main.qml qml/MyApp/pages/LoginPage.qml RESOURCES assets/fonts/Fredoka/Fredoka-Regular.ttf assets/icons/logo.png ) StackView { id: stack anchors.fill: parent initialItem: "qrc:/MyApp/pages/LoginPage.qml" <-------------- } So, as I understand it, we specify the URI MyApp (Which gets loaded in main.cpp as a module) and then append the alias you give it in the set_source_file_properties()

Hi and welcome to devnet, Glad a solution has been found and thanks for the follow-up ! You can mark the thread as solved yourself using the "Topic Tools" button or the three dotted menu beside the answer your deem correct :-)

const QQuickItem *rootObject = m_logWidget->rootObject(); m_logTextArea = rootObject->findChild<QObject *>("logTextArea"); const auto *quickTextDocument = qvariant_cast<QQuickTextDocument *>(m_logTextArea->property("textDocument")); auto *textDocument = quickTextDocument->textDocument(); textDocument->setMaximumBlockCount(10); Setting on C++ side works for me.

I'm not sure what is the question. You are creating a Popup and that's the correct approach to have something above the rest of your content. You also set the close policy according to what I assume is what you want. As you also identified, your dynamic object creation can be improved. My rule of thumb: don't ever use Qt.createComponent, and use createObject lightly. I'd argue here that using createObject is the correct approach for creating a popup. You can just use a declaratively created Component instead. As for creating items from a list, you should use a ListView or a Repeater instead. With a DelegateChooser if you need different delegates.

Hi, Intuitively, I would say you are using it correctly Likely an unintended consequence I would think so You should check the bug report system to see if this is something known. If not please open a new ticket containing a complete minimal buildable example showing this.

Did you get that to work in the end? From: https://doc.qt.io/qt-6/qrhi.html "writing to a dynamic buffer multiple times within a frame, in case such buffers are backed by host-visible memory, will result in making the results of all writes are visible to all draw calls in the command buffer of the frame, regardless of when the dynamic buffer update was recorded relative to a draw call"