@hackerturtle Set QT_LOGGING_RULES=qtc*=true environment variable and start DebugView. This way you can capture all the Qt Creator logging, and you should be able to find out what is going on.

Actually I've just found our solution here https://forum.qt.io/topic/157255/getting-debug-heap-correction-from-destructor-of-qstringlist/19 I seems that our camke config has not been linking msvcrtd.lib

Hi, and welcome! @Morty56 said in About the position of engine->rootContext()->setContextProperty() and engine->load() resulting SEGFAULT: What I've done is just move one method to another by integrating two functions to resolve this issue. Nothing else has changed. Here is my code. Which part could bring the result of segmentation fault? I am so confused. Your code could contain a race condition, where moving functions around changes the outcome of the race. Check your code using tools like ASan and TSan.

Indeed! As soon as I killed the adb processes, the freezes stopped immediately. Thanks a lot, you really saved my day!

@Kent-Dorfman I don't think so, because in the same implementation I use the <=> operator with a member variable that is of type int. Additionally, there is no problem with the usage of std::strong_ordering and the project uses other C++20 features. The compiler complaints only about those Qt types using <=>.

Hi, In addition to @hskoglund, Nuitka commercial seems to also offer that service. However I can't comment on it as have not used it.

Hi, Some things to check: which version of VTK did you install ? Meaning, is it the one for Visual Studio ? did you try with their latest version which is the 9.5 series ? as silly as it may sound, are you sure that this version has Qt support enabled ?

@JonB said in Qt Creator editor: Can we insert a column of sequential numbers?: Purely ooi, why does it change from cardinal words to ordinal ones after SEVENTH? :) Because: @cristian-adam said in Qt Creator editor: Can we insert a column of sequential numbers?: This works with ... AI :))

@Jammin44fm said in Problem running application on Linux. Ubuntu 22.04 LTS + Wayland platform.: Does this mean I will need to distribute a different version of the libQt6WaylandClient for each version of Qt that i'm using? To make it simple - yes. The ABI promises Qt makes are for applications making use of published APIs. They do not extend to different modules of the framework itself - you should never mix say QtGui 6.8.1 with QtCore 6.8.0; same for QPA plugins (as they make use of private API). Basically, when bundling Qt for distribution - you must copy ALL modules and plugins that the application uses, and not allow any to be used from the containing system. QtWaylandClient included in that - though it needs to be usually manually included as tools scanning dynamic library dependencies often can't see it. What is the status of the linuxdeploy-plugin-qt? it doesn't look like it's part of the official Qt package? It is not official. It works, I use it. As for status, I believe it is actively maintained, although as with pretty much all AppImage tooling it is done by one guy in a basement. Deploying Wayland plugins with linuxdeploy-qt has to be done with care. It works for me by including waylandcompositor in the EXTRA_QT_MODULES environment variable.

[image: b3140f50-9678-499a-8257-7bffe2cbd200.png] [image: 7f4a47e0-cccc-4b09-b11a-20ae23c69ef9.png] If the code within the signal handler is the same, the program can be compiled but it will fail to run and even cannot be debugged.

Hi, Are you using a static build of Qt ? If not, did you deploy the corresponding plugin and library along your application ?

@SGaist 6.9.1 + vs2022

Thank you, I'll have a look at its code to mimic its behavior.

Since items can only be dropped on a drop area, just connect to all drop areas' dropped signal. The signal is emitted with a drag event argument, from which you can establish the source, e.g. the dragged object. Have in mind though, that a drop doesn't cause reparenting automatically. So technically, there is no new parent, unless the app sets it explicitly.