Qt Creator and other tools

Restarting Qt Creator could also help. Qt Creator 15 will work better in this regard.

I've pointed out Batch Edit... in your screen shot:

qtcreator-qgis.png

@JonB Interesting, thanks. I always thought of NTFS as case insensitive per se.

@Programist said in Glitched integrated terminal on Windows:

@JonB Unchecking Use internal terminal fixes the problem

As I said, I have never used Use internal terminal. and never had a problem with the normal, external terminal. And that option was only added to Creator a while ago, it never used to have an internal terminal.

Try using the Ninja CMake generator. Alternatively you can disable the Lua plugin if you don't need it. -DBUILD_PLUGIN_LUA:BOOL=OFF

@cristian-adam Thanks for your suggestion.
https://bugreports.qt.io/browse/QTCREATORBUG-31996

@Ashutosh_Singh said in In installed QT creator but in kit not showing the any packages help me how to resolve this issue:

In installed QT creator

Did you also install Qt?
And please mention the OS and how you installed Qt.

Qt is not using doxygen but QDoc: https://doc.qt.io/qt-6/qdoc-index.html

As always with a "crash" and C++, run under debugger and look at the stack trace pane when "crashes".

@cristian-adam said in "Check code syntax“ not work after new setup!:

Make sure you use clangd.

qtcreator-use-clangd.png

Too correct Too right, that was indeed the cause of the problem. It's fixed now, thanks a lot!

@mashuo said in Hundreds of TMP files in workspace:

So, how to solve this problem?

Since this is a Windows problem that is not easy to reproduce, I can think of:

disable antivirus usage of a Dev Drive using WSL2 with Linux to cross compile for Windows either using MinGW or msvc-wine using a different operating system than Windows (Linux or macOS)

@epoli OP answered: file was 0 size and delete/rebuild solved it, what else to say?

You haven’t provided a single example of a mistake in Qt Creator. You just claim that it has mistakes without any proof. Same for the online installer, that you mentioned now.

Then you conclude, again without any proof, that „your company“ has stricter QA than Qt.

All of these statements are untrue.

differing versions of gdb have caused this for me, sometimes i'll be locked out of an entire set of libraries because qtcreator just doesn't 'play' with some versions of gdb from what I have found, because when people change stuff they forget that other programs just might depend on the way that data is displayed. If qtcreator gets data in a format it isn't expecting and therefore cannot properly format, or asks gdb for something in a way that it no longer supports, it will fail back to <not accessible> this problem has existed for quite some time (i came back about 6-7 years later to find this has not improved much, though it is a little better than it used to be)