General and Desktop

Also you could simply use Q_UNUSED/[[maybe_unused]] in-code to suppress it, instead of disabling it at the compiler level.

The first thing you should do is avoid star imports. You don't know what you are pulling there and it makes your code less readable and understandable. Next, remove everything that is not related to your current Qt issue. Deal with each problem one after the other.

@jronald It should not be hard at all, just a QTableView with a 2 column model. If it is hard to reproduce then something is going on/others will not be able to repro. As I say, I have used it many times with no problems, and don't you think other people would report if every time they tried to edit from a QTableView it went as badly wrong as this? Anyway, if it really does this (and I think you have something wrong in your code) I told you what you can do about it.

@SGaist Yes thank you.

@Mesrine It seems that the FIRST call to findpackage of Qt should have the QML component find_package(Qt6 COMPONENTS Core Gui Quick Qml) Because the qt cmake scripts use that to see what macros to include.

@wejgomi That is a pretty fundamental omission! Then I don't see how you had it working before you added the filter/setRecursiveFilteringEnabled() at all.

@Pedro-Vicente But using that script, gives a link error mocs_compilation_Debug.obj : error LNK2001: unresolved external symbol "public: static struct QMetaObject const QrwEmoticons::staticMetaObject"

@ChrisW67 Knowing it's called CBTProc does help a little at least. However, it is definitely not related to the code. Even a clean, newly created project gives this output. I've also reinstalled Qt to no avail. Is it possible for something external to Qt to cause this?

@jsulm said in what is auto generating LIBS path in makefile "qt creator": @micha_eleric said in what is auto generating LIBS path in makefile "qt creator": i found /usr/local/Qt-5.15.13/bin/qmake Bellow you write something about Qt 6.6.3 - so what Qt version did you actually build and where did you install it? "qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in """ - was XCB plug-in enabled when running configure before building? "[[nothing, and no clue where qmake(qmake**) is" - where you installed your Qt build... Qt 5.12.12 build from QT creator offline install, which went to Home and somewheres sudo is needed, but did not have features that online install has Qt 6.6.2 built from Qt Creator online install, which went to Home and somewheres sudo is needed Qt 5.15.13 built from https://download.qt.io/official_releases/qt/5.15/, which has some in Home and somewheres sudo is needed

@KeithMarex Only after cross compilation that you will have that compatible version for the generic -linux you will need to have something like this in your Qt Versions [image: e735fc59-e75d-41b6-9bce-1844bf3e48b7.PNG]

@SimonSchroeder This is pain when you move the widget around very fast :D It will take one screenshot and render the image for every moveEvent. I think it will be laggy as hell.

@sierdzio OK. I'll make a note of it! Thanks.

@KK2022 You should also add header files. Building will work without I think, but QtCreator will not find the header files I guess and complain.

@jsulm You are right. My bad! Thanks for clarifying :)

@sprkxr said in QT Crash: Has anyone had the same problem? How to solve? C++ programmers have written code that crashes since day 1. You solve it by debugging your program. ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p READ_ADDRESS: ffffffffffffffff Application Error 0xc0000005 (Access Violation) while trying to access using a memory address 0xffffffffffffffff. This is a classic invalid/dangling pointer problem. There's a slim chance this is caused by using an incompatible Qt 5 library set with an executable but, since you provide absolutely nothing about the "large project" we can only speculate.

@AROH I guess you need to declare/register QVector<int>, see https://doc.qt.io/qt-6/custom-types.html

It was encoding problem. I don't know why, but I think I'm having trouble reading QGCExternalLibs.pri on the Korean windows (maybe some of the other foreign languages windows). It was unexpectedly difficult to find out because it was a problem that only occurred in one file. Case closed.