General and Desktop

@SGaist said in Can I charge customer to use Software if I have created Software using open source Qt?: Also, if you do any changes to Qt for one reason or another, you have to publish these changes. In addition to what @SGaist said: You need to have the source code of the Qt version that you used. You can either provide a written offer valid for at least 3 months for your customer to request the Qt source code (not your own source code). Or you provide the Qt source code in the same way as your software (if your software can be downloaded, place a download link to the Qt source code in the same place). A download link to someone else hosting the same Qt source code does not count. You have to host it in the same place as your software. Furthermore, the LGPL requires that the user is able to relink with a different Qt version. If you are using Qt's DLLs this is taken care of already as the user can just replace the DLLs.

@Christian-Ehrlicher Thank you for your answer.

@clarify said in Menu bar questions: Question 2: Why, if I add the menubar at the wrong time, does its height() function return the window height? As @Christian-Ehrlicher says it does not matter what order you add things in. However, visual measurement functions like height() may not give you a meaningful result until the menubar/widget is actually shown, so if you are querying it before then that might be the reason.

Hi, If anyone here has any experience or knowledge related to this issue, I would be extremely grateful for your input. Even a small suggestion or a nudge in the right direction could make a significant difference for me.

@SGaist Yes in case of Qt 6.5.0, but this also happens with Qt 6.3.1, although the error I can read from QMediaPlayer is different: Qt 6.5.0: QMediaPlayer::ResourceError Qt 6.3.1: QMediaPlayer::FormatError Edit: The root cause of this issue was connected to file types and the way my url was constructed. I opted to use the native darwin backend with Qt 6.5 instead of the new ffmpeg, at least until 6.5.1 is out and I can do further testing. Thank you for the valuable input (as always!).

@Axel-Spoerl That's what I was fearing, but thanks for confirming.

@Christian-Ehrlicher Feels like: "I've been there... multiple times" :) @AnneRanch Somewhere in your code you are accessing an element from a QList which is not available (like 12th element out of a list from 0-10). index out of range This doesn't mean that you have a variable named index. It only tells you what happend. The index could be i or x or bananas.

Hey guys! I was in a similar situation, where I wanted to work on both Creator and Design Studio at the same time. I got a setup working that allows me to do so. Basically, I created a Design Studio project. This created a bunch of files and automatic things that lets Design Studio build/run the project. I then also created a Qt Creator project with its own cmake files and everything. The general file structure is as follows: parentQtCreatorFolder --Main.cpp --CMakeLists.txt --cppSrcFolder (contains handlers and rest of app) --qmlSrcFolder ----DSProjectFolder (ENTIRE project folder that DesignStudio generates) ------DSProject.qrc (created this using DS's export function) ------ all typical DS project files along with my qml using the standard defaultimports/content/etc structure In parentQtCreatorFolder's CMakeLists, I target the qrc file so that QtCreator knows where to find my QML resources # App import dirs list(APPEND QML_IMPORT_PATH "${CMAKE_CURRENT_SOURCE_DIR}/qml/DS_Project/imports/DS_Project") list(APPEND QML_IMPORT_PATH "${CMAKE_CURRENT_SOURCE_DIR}/qml/DS_Project/content") set (QML_IMPORT_PATH ${QML_IMPORT_PATH} CACHE STRING "Qt Creator extra qml import paths" FORCE) # Executable target file(GLOB_RECURSE SOURCES "./cpp/*.h" "./cpp/*.hpp" "./cpp/*.cpp" "main.cpp") file(GLOB_RECURSE QML_SOURCES "./qml/DS_Project/App.qml") file(GLOB_RECURSE LOCAL_QRC_FILES "./qml/DS_Project/DS_Project.qrc") add_executable(my-app ${SOURCES} ${QML_SOURCES} ${QRC_SOURCES} ) With this, I was able to target the correct qml resources in my app's main.cpp // Set engine to look for subfolders which could be modules engine.addImportPath(QStringLiteral("qrc:/")); engine.addImportPath("qrc:/imports/"); // Adding imports paths engine.addImportPath("qrc:/content/"); // Adding imports paths // Load main.qml from path with respect to current main.cpp engine.load(QStringLiteral("../QtCreatorParentFolder/qml/DS_Project/content/App.qml"));

@giorgik63 said in Where to put my plugin to be seen in Qt Designer ?: but how long will I have to wait ? You should ask the QtCreator devs if you want to know it exactly. Or simply compile your plugin with Qt 6.4

@Axel-Spoerl Fix is in the oven. (I'm not always that fast, so don't tell anybody ;-)

Before creating QApplication, QWindow objects, it's needed to add platform-specific QPA (Qt Platform Abstraction) Plugin support. In order to add it, it's needed to pass the PluginClassName as a parameter of the Q_IMPORT_PLUGIN macro Q_IMPORT_PLUGIN(PluginClassName ); The PluginClassName can be taken from the table below [image: 24517737-c60f-47b6-90a1-9a866bd8776d.png] https://doc.qt.io/qt-6/qpa.html In that case (Could not find the Qt platform plugin "cocoa" in "") before creation QApplication object it's needed to add macro Q_IMPORT_PLUGIN with QCocoaIntegrationPlugin parameter: Q_IMPORT_PLUGIN (QCocoaIntegrationPlugin); It works fine!

@JoeCFD Thx a lot! Got signed for it. If someone interested there are some info https://doc.qt.io/qt-6/best-practices.html https://www.qt.io/resources/videos/best-practices-in-writing-applications-in-qml-user-interface-qtws21 https://www.qt.io/resources/videos/qml-c-architecture-best-practices-qml-tips-for-efficient-development-dev-des-2021 https://doc.qt.io/qt-6/qtquick-bestpractices.html

@JoeCFD said in Errors in migrating from Qt5 to Qt6: background().color().red())); Thanks Joe, indeed that worked!

@Guy-Gizmo i think you selected the right one.

I don't have an answer yet with regard to the dollar issue but in the meantime, would using backticks around the command be a workaround you can use ?

You're welcome ! Since you thing working now, please mark the thread as solved using the "Topic Tools" button or the three doted menu beside the answer you deem correct so that other forum users may know a solution has been found :-)

@Saviz not directly no, that's something you need to build on top of it.

HEADERS and SOURCES has not much to do with the INCLUDEPATH With HEADERS and SOURCES you define which headers and sources belong to your project. With INCLUDEPATH you define which (additional) include paths should be passed to the compiler.