Qt Creator and other tools

me too !

image.png

image.png

@Christian-Ehrlicher said in Fake error with structure:

What code model do you use? If it is not clang but the internal

I don't understand what do you mean. I've download Qt Creator 15.0.0 here: https://github.com/qt-creator/qt-creator/releases I have CMake 3.27 and MinGW 14.2: https://github.com/skeeto/w64devkit/releases. I just want to use pure C language with CMake. I've created a project like this:

b0164e6d-2acb-4997-b39c-2e96f46fc618-image.png

0804f311-1fd7-4159-a4b4-6cd5f7cc53aa-image.png

I am facing the same issue too

https://bugreports.qt.io/issues/?jql=project %3D QTCREATORBUG AND text ~ "focus freeze" pointed to https://bugreports.qt.io/browse/QTCREATORBUG-28957 but this was fixed in Qt Creator 10.

Hi and welcome to devnet,

That looks rather like a bug.

Did you already check the bug report system for something similar ?

I have solved this problem by installing the same version of qt creator in the original directory and then uninstalling it

@surfcius , @Christian-Ehrlicher
In my code as pasted, Creator 13 I think (unless it's 11?), clang code completer too, I do not get that warning in the IDE. I don't believe I have touched any clang settings, I suspect my C++ is C++17. Why do I not get it?

https://bugreports.qt.io/browse/QTCREATORBUG-32191

@Perdrix
Yes, I think message

qt.qpa.xcb: could not connect to display

is the clue. I think that when xcb fails to load, their misleading message about libxcb-cursor0 notwithstanding, you get an explicit "failed to load" but not "could not connect to display". I think you only get that one when DISPLAY is wrong.

Hi @jsulm
Thanks for you response :-)

I think i have setup the sysroot correctly. In the "Preferences" -> "Kits" and under the Sysroot, i have defined:
/opt/fsl-imx-wayland/6.6-scarthgap-imx-full-image/sysroots/cortexa7t2hf-neon-poky-linux-gnueabi

@Jalim_Rabei Kits is a QtCreator thing. You just need to install Qt and in case you installed Qt for MinGW on Windows also MinGW. QtCreator will detect installed Qt versions and compilers and create Kits. You can modify these Kits or create new Kits by yourself if needed.

I can see it at https://bugreports.qt.io/browse/QTCREATORBUG-32176 Thank you.

Thank you. Please comment there with the details of the computer running. Memory, CPU, etc. Was the project using a remote device and so o.

I haven't seen this in practice. Please do open a bug report at https://bugreports.qt.io/secure/CreateIssue.jspa?pid=10512

I do have Python on my Windows machine, it's autodetected, but makes no issues:

$ where python C:\Users\Cristian Adam\AppData\Local\Programs\Python\Python312-arm64\python.exe C:\Users\Cristian Adam\AppData\Local\Microsoft\WindowsApps\python.exe

If you don't need Python, you could disable the Python plugin. You could have a Qt Creator shortcut that does the equivalent of:

$ qtcreator -noload Python

I'm using Qt 6, MSVC 2022, qmake. I had to add this to the .PRO file:

QMAKE_CFLAGS += -std:c++17 QMAKE_CFLAGS += -Zc:__cplusplus

At https://stackoverflow.com/questions/29826101/how-to-restart-adb-manually-from-android-studio we learn that one has to do a:

$ adb kill-server && adb start-server

You could have this in a script that start Qt Creator, or in Qt Creator as an external tool.

Hehe. I've found the reason! My source tree contains a 3rd party library, which I updated recently. The new version would include an example showing how to use it with QML. Now, androiddeployqt is running qmlimportscanner with the root directory set to the source tree. Thus it will find this (unused) example code and stuff it's dependencies into the APK, nearly doubling the size.

I could get around that by specifying QML_ROOT_PATH in the project file.

You are right, the layout in "scrollAreaWidgetContents" solved the problem. Thank you very much.