Solved in PySide 6.11.2

@Malachi said in The required XCB cursor platform library was not found! Please use your distribution's package manager to install it.: I've been bonking into this error (warning?) for years. Are there no suggestions how to repair it? The error message tells you how to repair it: By installing the XCB cursor library. sudo apt install libxcb-cursor0

@Malachi said in The required XCB cursor platform library was not found!: I've been bonking into this error (warning?) for years. Are there no suggestions how to repair it? Do you mean the warning about XCB cursor being not found? The solution is to install the missing library. On Ubuntu 22.04, you want sudo apt install libxcb-cursor0

Hi, AFAIK, no. The most simple is to update your CMakeFiles.txt and either comment out the lines with the files or delete them.

Thx! Guess it is better to start with plain .cpp and .h file for now.

I made a bug report and added more details here https://qt-project.atlassian.net/browse/QTBUG-143646?focusedCommentId=2611561 but they haven't updated it yet, what do I do?

@JKSH I've made some progress - merged my changes from QtSvg 6.10 into 6.12. Also tried rebase (on a separate copy), but rebasing is a separate sorcery skill I clearly do not possess at the moment. The merged version builds, but my CMakeUserPresets got lost somewhere in the merging, and now Qt Creator builds everything in the repo/build directory. A minor inconvenience, but tolerable. Running tests and examples against the new build (and ensuring they are run against the new build) needs more time. I remember trying my previous CMake build with a custom LD_LIBRARY_PATH to ensure it uses the right stuff. Maybe it will be applicable in this case as well. Qt Creator likely has env variables somewhere in the Project settings, haven't explored those yet. The AI that I poke with different stupid questions also suggests that I can try ldd /path/to/your/example | grep Svg to verify that the example/test will use the correct library before running it. I'll circle back to this thread when I have more info to share.

@DuBu your model will not update in your qml gui without Q_OBJECT macro in TableModel. I did not change anything in your code and it works on ubuntu .

Hi, Approach 1 is correct. MainWindow does not need to expose its internal structure in this case. In fact, it is pretty rare that an application main window exposes its internal state like for your solution #2. One other good point is creating your API client outside of MainWindow. This allows scenarios such as passing a fake API client for testing purpose if for any reason you cannot contact/spin up your backend server. This does not seem to be the case here but still it can be useful.

Thanks for the clarification. That explains the behavior. The limitation makes sense for my use case (Qt used as a plugin inside a non-Qt application). I had interpreted the documentation to mean that, as long as only one QApplication instance exists at a time, recreating it in a different thread would be supported. Knowing that QGuiApplication leaves behind internal objects tied to the first thread, making cross-thread recreation currently impossible, answers my question. I'll adjust the design accordingly. Thanks for the detailed explanation and the Qt bug reference.

# --- מציאת Qt6 לפני include(QtInstallPaths) --- find_package(QT NAMES Qt6 REQUIRED) find_package(Qt${QT_VERSION_MAJOR} REQUIRED COMPONENTS Core Widgets UiPlugin # נדרש לתוספי Designer — הסר אם לא רלוונטי Designer # נדרש לתוספי Designer — הסר אם לא רלוונטי )

@Joe-von-Habsburg said in Elided settings limit error: any solution here? due to settings limit So did you check the settings for such a limit?

It seems to be a bug. Reported 2 years ago. https://qt-project.atlassian.net/browse/QTBUG-127124

Hi, Which version of Qscintilla is that ? With which version of Qt ? Can you provide a minimal compilable example so people can reproduce the situation the same as you do ?

Maybe you can compare the cmake files from Qt for Qt6.11.0 and 6.11.1 to find a differerence which may affect the manifest generation. /edit: This looks promising: --- a/cmake/QtBaseGlobalTargets.cmake +++ b/cmake/QtBaseGlobalTargets.cmake @@ -459,6 +459,13 @@ elseif(WASM) "${QT_BUILD_DIR}/${INSTALL_LIBEXECDIR}/qt-wasmtestrunner.py" @ONLY) qt_install(PROGRAMS "${QT_BUILD_DIR}/${INSTALL_LIBEXECDIR}/qt-wasmtestrunner.py" DESTINATION "${INSTALL_LIBEXECDIR}") +elseif(WIN32) + qt_copy_or_install(FILES "cmake/windows/app.exe.manifest.in" + DESTINATION "${__GlobalConfig_install_dir}/windows" + ) + file(COPY "cmake/windows/app.exe.manifest.in" + DESTINATION "${__GlobalConfig_install_dir}/windows" + ) endif() # Install CI support files to libexec. --> https://codereview.qt-project.org/c/qt/qtbase/+/718374 If you find a solution which works for cl and clang-cl it would be nice.

Vector-based formats are usually superior to pixel-based formats. SVG is a vector format, so it is generally preferable to use a vector image. This allows the image to scale properly to different screen sizes.

Does your software have a style sheet set up somewhere?

thanks, Awesome Programmer, i somehow missed that line.

What you say is true, it's an oversight. That does not solve the issue I am having though: the dialog opens when compiled to desktop, not when compiled to WASM.

The idea of the QValidator is to validate while you are typing/changing the value. If you just want to validate at the end (not while things are changed), then you can just write a function that goes over all the widgets. I remember a talk by an Adobe employee that was about something similar. AI tells me the speaker is Sean Parent and the library is Adam (a.k.a the Property Model Library or PML) which is part of the Adobe Source Libraries (ASL). Maybe you can find it and adapt some of their ideas. It is not explicitly written for Qt and might not work with it out of the box.