Qt Creator and other tools

@jsulm We are only allowed to connect to our company's git repo in PC A, and the pc b are not allowed to connect to the git repo. So I want to find resolution to deal with this problem, just like plugin remote-ssh in vscode. Now I am using NFS.

At QTCREATORBUG-29942: <name>~XXXX.TMP files are created and not deleted when saving files on FAT32 there is a similar issue. The solution was to set the environment variable QTC_DISABLE_ATOMICSAVE to 1.

@m0xf Please read the documentation: https://doc.qt.io/qt-6/qqmlparserstatus.html#details "To use QQmlParserStatus, you must inherit both a QObject-derived class and QQmlParserStatus, and use the Q_INTERFACES() macro."

This seems to have done the trick, as a workaround. I'll try to get more details & follow up with sometime useful for a bug report. Thx for the quick pointer!! QT_QPA_PLATFORM=xcb qtcreator

@Noobish said in A single project that builds multiple executables: The benefit would be not having to sync changes to the common code between the two projects and compiling everything would perhaps be quicker since when a common class has been compiled it does not have to be compiled again (I guess)? Put common code into a library (which would be yet another project) and link against this library for these two executables. Or, like @Christian-Ehrlicher said, combine all projects into one. Even then, it would make sense to have one library and two executables as build targets.

@cristian-adam said in Increase font size of the project files tab: See here https://forum.qt.io/topic/153476/how-to-increase-qt-creator-font/3?_=1747559433165 It worked. Thanks!

@Noobish For code completion the .ui must be processed by uic to produce the ui_....h file as C++ code. This should happen as part of build, every time you update the .ui or force clean rebuild. There are many little things you can investigate: For qmake the .h file is generated into the build output directory (where object and executable files are). I do not know for cmake, where you say you found it may be reasonable. Make sure there are no other instances of that file elsewhere which could be picked up. Update the .ui, do a build, verify the timestamp on the .h has been updated. Read the .h into Creator and have a look through it. It's just C++ code. Verify you can see the lines generated for the components you add. Forget about code completion for a moment. Type in what (you believe) is right to access some new ui-> element in your code. Do an actual compile/build. If that errors on your new component you are doing something wrong; if that succeeds but the code completion does not you have some problem in the latter area. Do a complete delete and rebuild. Create a brand new, standalone project elsewhere and see how you get on with creating new components.

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.