Qt Creator and other tools

So it's exactly the same as for embedded systems. You cross-compile, copy and execute. Otherwise you also have VS Code (or alternatives) that have a remote dev feature through tunneling and some additional software installed on the other machine.

Use a debugger and set a breakpoint in qsslsocket_openssl_symbols.cpp/tryToLoadOpenSslWin32Library: https://code.qt.io/cgit/qt/qtbase.git/tree/src/network/ssl/qsslsocket_openssl_symbols.cpp?h=5.3

I found that turning off the "Clang Code Model" plugin returned qt creator to normal operation, without the need for the QT_QPA_PLATFORM=xcb workaround.

@pi-squared said in Menu bar menu so long it cuts off, making me unable to add more buttons. (Yes, I'm being serious.): It works looks fine when running it, though. Do I understand that correctly - the first screenshot is from the Widgets Designer as part of Qt Creator, the second is from running the compiled executable? If I create large menus, I usually do it programmatically, not in Widgets Designer. I'd probably use a static constexpr std::array to store menu texts, maybe use a struct as a type that tells me whether a menu's action is enabled by default. Maybe I'd even keep an enum around that has a key for each action. Just loop over the array and add actions. That's much easier to maintain, than to change an entry in Widgets Designer. It hasn't been programmed to handle super large menus...

I forgot to mark it as solved

Thank you @cristian-adam That is exactly what I needed. (I searched the documentation website for that environment variable and found nothing. Where should I be looking for information on useful environment variables for Qt tools?)

@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."

@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.

@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.

@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!