Qt Creator and other tools

I presume with "Qt" you are referring to Qt Creator? If so, there's a debugger log, right hand side of View->Views...->Debugger Log. Maybe there's something interesting in there. Also, is this the "internal" or the "external" terminal?

@Christian-Ehrlicher To be fair the OP reports Running in debug mode, qDebug() doesn't show messages in Qt Creator/Application Output, but when running a terminal manually, it shows. Assuming the executable is compiled the same (e.g. either debug or release) whether it is run from Creator or from a terminal how would some "external logging config" allow for output to terminal in the latter case but not the former? Unless you mean the environment differs such that this logging file is picked up when running from Creator but not outside? @jronald You might verify that if compiled for release instead the behaviour is the same? Also if executed from Creator but as Run rather than Debug does that make any difference?

@asenzz It has been mentioned in the past that the Android plugin could be the cause of short freezes. But we do need to know more details.

@cristian-adam Thanks for the input. I've looked at the code of ksyntaxhighlighting, qt-creator and kate and and could not make much sense of it. Meaning I could not track down the place where "attributes" would be read or used from the zig.xml file. After trying out more color schemes in QT Creator again it seems like "modifiers" are mapped to "locals", which apparently comes from KSyntaxHighlighting::Theme::Variable, but I don't yet see the connection in the source. @SimonSchroeder Unfortunately that's not working for me. I'm on Qt Creator 17.0.1 and in the end it looks like "locals" is what I was looking for. Not sure how I missed that earlier and appreciate the input!

@clashdle In Qt Creator, the default Ctrl+/ behavior adds // at the beginning of each line and isn’t directly configurable for QML comments. However, you can use block comments (/* ... */) in QML to achieve a custom style. For example: TextField { id: textField width: 200 height: 40 background: Rectangle { color: "lightgray" border.color: "black" border.width: 1 radius: 4 } contentItem: Text { /* anchors.fill: parent text: textField.text color: "black" verticalAlignment: Text.AlignVCenter leftPadding: 10 topPadding: 10 // adjust as needed */ } }

Hmm odder and odder - I ran the build again and it worked!

@873578156 said in My terminal is currently displaying a blank screen,: me too and long time。 Not to be rude but this does not help. Both @cristian-adam and me asked for more information to help you so please provide them.

The culprit seems to be the "File system" view in the left panel. It wants to display the whole tree where the file is located which happens to be the nix store. Mine contains 34046 directories at the moment. This all happens on the UI thread, blocking the whole UI. The workaround is to close the "File System" view.

@paulf Hi, While the installer itself is indeed x86_64, the Qt installation is universal.

@aha_1980 Instead of just trying the codes in my own batch file, I changed the name from echoansi.txt to echoansi.BAT and set that as the custom process step, and it worked fine. However, when I tried to use the same codes in my own batch file, I noticed that some combinations of colors just won't work -- others are fine, but not what I need. For example, the Qt Creator output doesn't seem to recognize the codes for yellow (or bright yellow) background, nor for white or yellow text on a dark background -- although these look fine in the echoansi.BAT output. I need to look at this some more. At least it is nice to know that the endeavour isn't totally hopeless! Thanks for your input, @aha_1980!

Hi, just wanting to see if this was ever solved; I'm having the same issue, too. EDIT: I reloaded my VSCode Window (after checking to make sure that ~/.local/share/CMakeTools/cmake-tools-kits.json actually found the Qt installation in ~/Qt/. That fixed the problem somehow.

You can manually configure a Kit in Qt Creator by adding a C/C++ compiler, a Qt setup, a Debugger. Or you can do it from command line via the SDK Tool.

See https://doc.qt.io/qtcreator/creator-copilot.html for details and tell us if it worked!

In the Analyzer preferences page, there is the: Prefer .clang-tidy file, if present. You could uncheck it and see how things work.

I turns out the the moc*.cpp files are included at the end of the regular cpp files. So the question now becomes how to tell VS Tools to run moc, but NOT to compile the moc*.cpp files.

Qt Creator 18 added experimental devcontainer support: https://www.qt.io/blog/qt-creator-18-released

Start by doing the steps described at https://doc-snapshots.qt.io/figmatoqt/figmatoqt-getting-started.html

Hi, This is a user forum. For feature request, you should open one on the bug report system.