QML and Qt Quick

Let's start with the basics: Which version of Qt are you using? On which operating system are you working (Windows?)? What functions do you call to minimize, maximize or close your app?

@JKSH said in How to customize the attached ToolTip?: The workaround is to call QQuickStyle::setStyle("MyStyle"); in C++ before initializing the QML engine. And if you have a custom style not entirely compliant with Qt Quick Controls or you don't want to switch all your controls, you can hack it by setting the _q_QQuickToolTip (and _q_shared_QQuickToolTip) property of your QQmlEngine to an instance of your ToolTip before loading your QML files (no guarantee it works in future versions). As mentioned in https://qt-project.atlassian.net/browse/QTBUG-107684

@poncho524 said in qml javascript function parameter typing: is there anywhere in the docs that explain when specifying type became acceptable? i can't find it. Not the docs, but this blog post says it was introduced in Qt 5.14: https://www.qt.io/blog/compiling-qml-to-c-annotating-javascript-functions https://www.qt.io/blog/compiling-qml-to-c-annotating-javascript-functions Not that I know of

Fixed it by checking system environment variables, be careful about old QML_IMPORT_PATH and QT_PLUGIN_PATH

@Zapfyr said in QT QML How to chain QAbstractListModel and QSortFilterProxyModel: Limit the output to X items. This sounds like the job of the view. Provide space to display X items, and omit the ability to navigate further.

I did ts_calibrate many times and in ts_test also working only

Indeed, this was a bug. More info here, in case anyone else comes across this: https://qt-project.atlassian.net/browse/QTBUG-145124

I haven't used TableView in Qt 6 but I wonder whether your use of RowLayout in your delegate is necessary. Not saying it is causing the issue but it might be worth simplifying your implementation by removing it and debugging from there.

I think it follows your system theme because on my system it uses the dark theme already

I believe globbing is supported by CMake but that it is generally recommended not to use it. As a CMake newbie myself I have followed what seemed to be the prevailing wisdom and stuck to hard coded lists. One compromise that I did come across was to read the file list from an external file, e.g., file(STRINGS "sources_list.txt" MYSRCS) and then use the MYSRCS variable as your file list in CMake commands (e.g., add_executable(my_app ${MYSRCS})). This would mean maintaining the "sources_list.txt" file externally but that would be easy to automate. I haven't actually tried this though so take all this with a pinch of salt.

Oh, so the issue has to do with Microsoft. Thank you for your help J.Hilk!

@JoeCFD I am switching to CMake because it is the official Qt build tool and it is supported by Qt Creator. The documentation is increasingly defaulting to assume you use CMake and the online support such as offered by this forum contains advice about CMake. I used qmake when that was the official build tool because that was the path of least resistance. I am using CMake now for the same reason.

How much does it affect you if the graph's boundaries grow by one unit? If the graph is drawn correctly, there shouldn't be a problem.