Qt Creator and other tools

@cristian-adam said in "Check code syntax“ not work after new setup!: Make sure you use clangd. [image: eb694094-6999-4062-8e2a-d6143b89d36b.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)

Have added Geany as an external tool for this.

@Bazinevis You can check every module of interest yourself. The documentation page either claims it to be LGPL, GPL or Commercial use only. Also AFAIK when using the Online Installer with your non-commercial community account, you only get to see modules and features that are available for you.

@Pl45m4 Thanks for taking the time tonight. Yeah, the QT framework is pretty fun to work with all in all! Yes, random crashes, and the only error messages I got just led me in circles around the forums. The issues with the IDEs (they all seem largely like the same basic software to me, BTW) are pretty widespread, and not much luck on true fixes. The other part that was just great was that they'd eat my files when reading them while crashing, so I'd lose all my code! Agreed that I was really only in it for the WYSIWYG GUI tooling. I lean (very heavily) toward backend development, and design has never been my forte. So I was bummed to lose that, but must admit that the build tools work swimmingly in VSCode, and I'm having fun nonetheless. The ever-growing nerd beards on the Arch forums didn't have much to offer. There were a few folks saying they couldn't reproduce the bugs (segmentation faults are really hard to diagnose). But many more saying they had also decided to throw it out the window. I'm mainly in it for the KDE plug-and-playness. I doubt I'll end up being a pro QML dev, but it's been a fun little jaunt (kinda). But yes, great point, I'm doing just fine in good ol' VS Code with the wonky little QML preview CLI tool on an auto-refresh!

To anyone who comes across this, you need to put the arguments into a list [arg1, arg2, ... argN].

That's unfortunate. I have a vague recollection of a similar problem with the Quick compiler. Build-time selection such as per-Qt version resource files might work.

@dclark064 said in PRO File Does Not Load Project into Qt Creator: Qt 6.7.2 Then you won't have luck with the app you're trying to compile as it needs Qt5 due to xmlpatterns

@Axel-Spoerl thnks not see at all .... I copy combobox stylesheet on qtcreator without correct it onto chekbox 😅 😅 😅 😅

I found the solution. The reason is border.... Thanks for all... ~~Warning: If you only set a background-color on a QPushButton, the background may not appear unless you set the border property to some value. This is because, by default, the QPushButton draws a native border which completely overlaps the background-color. For example, QPushButton { background-color: red; border: none; } See Customizing QPushButton for an example. ~~

@AbdelrahmanElShafay There is also no Qt version and CMake is unconfigured

@harveyab: Have you unchecked Edit > Preferences > Build & Run > General > Build and Run > "Abort on error when building all projects"?