Qt Creator and other tools

@Noobish Have you (re-)run uic to (re-)generate the (now changed) C++ .h file?

Simply use a second add_executable()

As the error message tells you, you forgot to specify the source directory.

@Qreator35 you're missing a Qt version, that install folder should have a folder containing only numbers, representing the installed Qt Version, if installed via the installer/maintenaince tool: [image: 311a2309-9d8f-4465-ab1f-df7700ec55bf.png]

@davecotter Just scroll down to the x64/x86 versions

A slightly confusing and complicated way to ask: "How can I create a .h file from a .ui file manually?" The answer is: Use the uic executable as documented here. It's located in the libexec directory of your Qt installation.

[image: 981e5ed0-e827-4cda-a277-f8ad6c883443.png] As you can see in the picture... it just works 😅

@karl-police said in What does the Barrier Icon mean in Qt Designer? I just wanted to figure out how to fill a Frame to its parent window with Qt Designer: if I go to the top at "Forms" that I can give it a layout, I think, and that fixed the barrier icon. There are actually three (maybe even more) ways to set a layout. the layout buttons in menubar via object list/tree (what you show in your screenshot) by right-clicking on the form design itself

Hi, is there a way to remap this functionality from Alt+Up/Down and Alt+LMB to only the MMB (scroll press) button, same as in VSCode? I can't find the shortcuts under Preferences > Environment > Keyboard.

@Strife1817 said in Unable to continue with compilation. Need to build Qtlocation, in order to proceed.: that is compatible with requested version "6.10.0". I don't think Qt 6.10.0 is released already? You have Qt 6.9.0, so change your CMakeLists.txt to request that version instead of 6.10.0.

Just an addendum to this post: I closed Qt Creator after the above post. When I opened it again today to test the module functions, Qt tried to revert everything to GCC. The kits I had removed had come back, the default compiler was set to /usr/bin/gcc and every time I edited a file I got a dialog box asking if I wished to change back to GCC. I had to go into the build settings and manually edit the compiler line and set it back to clang and then the dialog went away. Am I really going to have to do this every time I want to use clang? Hopefully, GCC15.1 will be available soon on Homebrew and it will recognize modules and vcpkg packages properly!

There also seems no documentation at all. :( [image: 4aa812bc-ab00-47c2-bf6b-5baf97d26609.png]

@SimonSchroeder That's a very important point! I have solved my immediate problems like this: I deleted GCC-13 from the kits/compilers. I used sudo update-alternatives to make /usr/bin/gcc point to my GCC14.2 homebrew installation. That worked partially but GCC-14.2 doesn't handle modules properly and nor does it reliably handle vcpkg packages! (I have been using clang-19.1 with VS Code for the project/tutorials mentioned above and that does work) I struggled to get QtCreator to use the clang compiler but at last found the solution, albeit using a sledgehammer to crack a nut! Delete GCC entries from the Kits/compilers section. My Qt installation already found clang as it was in my path. Added 'export $CXX=clang to my .bashrc. Not sure how necessary this is but it was mentioned in an error message. 3)Added the line "set(CMAKE_CXX_COMPILER clang++)" to CMakeLists before "project(helloClang LANGUAGES CXX)" Now my little helloClang compiles with the clang compiler. I added a vcpkg statement and the fmt library with the appropriate lines in CMakeLists - and it works! I haven't had time to try out modules yet but I'm sure they will work as well. I don't think it was really necessary to delete the GCC kits, probably setting the compiler in CMakeLists may be enough. I will continue experimenting to see what works. None of this is necessary in VS Code, it's a simple drop-down menu to select the compiler when configuring initially. Also, there are no entries in the CMakeLists file nor environmental variables set. An equivalent in QtCreator would be to just go to the kits page and select the wanted compiler and click Apply/OK but this does not work. I'm just pleased that I will be able to use modules and vcpkg packages from QtCreator now.

@SGaist No, its not. Also, the OP is asking for Linux anyway. I just assumed that this might be something that other debuggers do as well.

@SuhasKrishanamurthy Big big thanks Brother .

@YamiTheWitch said in Cannot create object of QNetworkAccessManager: Doesn't Qt automatically change the cmake file? Qt is a C++ framework. QtCreator would be responsible for the build tools. But it would have to parse your code to figure out what modules you're using to and them to CMakeLists.txt file then.

@A123 So the "arguments" box does let you include > file? I am surprised, interesting.

A development release with an updated .natvis file that supports QMap >= 6.9.0 can be downloaded here: https://download.qt.io/development_releases/vsaddin/3.4.0/ Hope that helps, if not, please head over to https://bugreports.qt.io/ and file a bug report under the 'Qt Visual Studio Tools (QTVSADDINBUG)'

Thank you for the answers. Indeed it my creator was in the old Version 10. With the newest Creator I dont get this error. other errors but, for this I make an other thread -