Use a recent Qt6 version or use the windowsvista style.

I figured it out on my own. The Forecast widget can be promoted, and that promoted widget can be used in another ui file

@cristian-adam Hm strange i bet im doing something wrong. Would it be possible to provide your project via github or something with step by step instructions on what commands you use? Would really appreciate that, cause having to do this all over and over again manually really sucks. :D

@JKSH removing RESOURCE_PREFIX / is no problem, works still fine, thanks. :D However do you mean changing all mymodules mentions to mymodulesplugin or only this one? Cause when changing only one it gives me errors. Here are all my files: [image: ea7f99db-02e4-4cd6-b307-2682ee306007.png] CMakeLists.txt inside mymodules subfolder: cmake_minimum_required(VERSION 3.16) project(mymodules VERSION 1.0 LANGUAGES CXX) find_package(Qt6 REQUIRED COMPONENTS Quick) qt_add_library(mymodules STATIC) # <--- STATIC instead of SHARED/PLUGIN qt_add_qml_module(mymodules URI mymodules # entspricht: import mymodules 1.0 VERSION 1.0 QML_FILES Buttons.qml Qmld.qml XP3DDebugViewer.qml SOURCES Myhelper.hpp Myhelper.cpp ) set_target_properties(mymodules PROPERTIES QT_QML_MODULE TRUE ) target_link_libraries(mymodules PRIVATE Qt6::Quick ) Main CMakeLists.txt: cmake_minimum_required(VERSION 3.16) project(QmlLibraryTest VERSION 0.1 LANGUAGES CXX) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_AUTOMOC ON) set(CMAKE_AUTORCC ON) find_package(Qt6 REQUIRED COMPONENTS Quick) qt_standard_project_setup(REQUIRES 6.8) qt_add_executable(appQmlLibraryTest main.cpp ) qt_add_qml_module(appQmlLibraryTest URI QmlLibraryTest VERSION 1.0 QML_FILES Main.qml ) # Qt for iOS sets MACOSX_BUNDLE_GUI_IDENTIFIER automatically since Qt 6.1. # If you are developing for iOS or macOS you should consider setting an # explicit, fixed bundle identifier manually though. set_target_properties(appQmlLibraryTest PROPERTIES # MACOSX_BUNDLE_GUI_IDENTIFIER com.example.appQmlLibraryTest MACOSX_BUNDLE_BUNDLE_VERSION ${PROJECT_VERSION} MACOSX_BUNDLE_SHORT_VERSION_STRING ${PROJECT_VERSION_MAJOR}.${PROJECT_VERSION_MINOR} MACOSX_BUNDLE TRUE WIN32_EXECUTABLE TRUE ) # Baue und installiere das Sub‑Modul mit add_subdirectory(mymodules) target_link_libraries(appQmlLibraryTest PRIVATE Qt6::Quick mymodules # <-- statische lib (ohne "plugin") ) include(GNUInstallDirs) install(TARGETS appQmlLibraryTest BUNDLE DESTINATION . LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR} ) In Main.qml i import it as: import mymodules 1.0 Qmld { id: krass anchors.fill: parent } Buttons { id: neubtn anchors.bottom: parent.bottom anchors.right: parent.right }

@Mark-K-R-Walker If your header really looks like you showed us, it's no wonder you get compile errors: #ifndef SOUND_H #define SOUND_H ... class Sound : public QIODevice { Q_OBJECT private: QMediaDevices *AllMediaDevices = nullpointer; QAudioDevice DefaultAudioOutputDevice; public: Sound(); }; // <- Closing curly brace and semicolon are missing! #endif // SOUND_H Please add the }; before the #endif and try again. Regards

@JoeCFD Yes, Qt 6.9.0. I've referenced WinUI's approach, but I need help resolving this issue.

Setting the environment variable QT_DEBUG_PLUGINS to a non-zero value should result in information about the platform plugin loading to be dumped to the console. Sometimes it provides very direct and actionable feedback, eg reporting a missing dependency or version mismatch. Using QT_WIN_DEBUG_CONSOLE is probably also necessary. Further documentation: https://doc.qt.io/qt-6/debug.html#environment-variables-recognized-by-qt

This command worked for me sudo pacman -S libxml2-legacy

@cristian-adam said in Qt 6 compiles twice slower that Qt 5: But, the libraries are not there. See https://arewemodulesyet.org/ for the amazing progress that is being done by the community. This is gold :D Estimated finish in 2344

For QWidget Applications, will this ever be resolved - being able to stack QPushButton in front of a QVideoWidget, or must we always resort to QML and QTQuick applications? My application was already built as a Widget application. This is frustrating. I've spent many hours getting this to work. For my widget application, I have to throw in a dummy QQuickWidget in the stack (1px x 1px) just to get QT 6.7.3 to stack the QVideoWidget correctly inconsistently.

Hi, It's been a very long time since I looked at these part. Did you already took a look at the QRhi ? This was one of the big changes and I wonder if the changes related may have created a regression of your use case.

Hi, Why not use a setup like with embedded systems ? You build on PC A and then copy the executable and relevant libraries on PC B and do remote debugging.

@inbilla hi, Are you using custom models ? If so, are you also taking advantage of the last argument of the dataChanged signal ? This one limits the roles that the view should get data for in order to update itself.

Thank you @cristian-adam That is exactly what I needed. (I searched the documentation website for that environment variable and found nothing. Where should I be looking for information on useful environment variables for Qt tools?)

If I remember well, this SharedArrayBuffer is needed when using wasm multithreading. If your app does not need multithreading, use Qt wasm single threading. If multithreading is needed, check https://forum.qt.io/post/765010

@JKSH Thanks for answer, QT_QML_OUTPUT_DIRECTORY on top of qt_add_qml_module() really helped and now everything is working fine! @JKSH said in Correct way to make QML modules Qt 6.5-6.9: To use MButton, you need import UI.Components and not import UI.Assets my bad, my eyes were busy with the warnings and I didn't notice :) @JKSH said in Correct way to make QML modules Qt 6.5-6.9: QML_IMPORT_PATH is used by Qt Creator's old code model. It is not used by the new QML Language Server (qmlls). Likewise, QT_QML_GENERATE_QMLLS_INI is only used by qmlls and not the old code model. By default, you'll be using qmlls if: You're running the latest Qt Creator, AND You're using Qt 6.8 or newer for your project So can i use modules with "old" approach if I have Qt 6.5 and 16 creator? What is the difference when using without QMLLS on Qt 6.5? or is it the same, just don't write QT_QML_GENERATE_QMLLS_INI and add QML_IMPORT_PATH? @JKSH said in Correct way to make QML modules Qt 6.5-6.9: Note: There is no point linking your executable to Assets, Components, and Pages libraries because your executable does not use any C++ symbols from those libraries and if I use C++ in this module, as I understand it, I will just need to link these modules, and the behavior will remain the same?