Qt Creator and other tools

There is no way to do that at the moment. I've added a new "setChecked" function here: https://codereview.qt-project.org/c/qt-creator/qt-creator/+/698994 Feel free to comment or suggest other functions as well.

@cristian-adam Very interesting, thank you. It turns out there is some vsdbg.exe, which I take to be the actual debugger as its own executable. Which you can "drive", if you know what to send it. I didn't care about DWARF, PDB etc. I was interested in which debuggers allow a host to "talk" to them and vice versa, send it commands, read variables, etc. Which is what Creator will require. I know gdb can do it. I didn't know there was a standalone executable for the debugger from VS, I thought it was a built in.

Hi, The Qt Company had to migrate their Jira instance. Everything is explained in this Wiki article.

@jsulm In /opt/Qt6/doc/ there are two folders called config and global. The contents of /opt/Qt6/examples are shown in the picture below: [image: 3efa5588-09ab-4525-b95d-1680d94f7516.png] Both folders are owned by root and have their permissions set to rwxr-xr-x

@jsulm I wondered about that myself. But it does not seem to be the issue. I fixed it by installing the dependencies from @cristian-adam comment :)

@srimuthu I think you will have to implement this by yourself. If you move the scroll bar to the top to see older messages you need to fetch those messages and add them to the widget, then the scrollbar should adjust.

Starting Qt Creator with the QT_DEBUG_PLUGINS environment variable set to 1 might have shown the culprit.

Hi and welcome to devnet, Beside the suggestion of @JonB, another thing you can try is to start Qt Creator with -temporarycleansettings to see if there might be something off with the settings.

@cristian-adam said in QtCreator 18.0.0 often throws file errors when modifying code and Ctrl+S.: @Calcifer You could use Process Monitor with qtcreator.exe and find out what is going on when you get the message box. Thank you! I have got Process Monitor opening, and trying to add my workdir to the whitelist of anti-virus software, that should work.

@JonB Thanks include_directories(<include directory>) worked.

@sandmeteor, very helpful, thanks a lot!

@Sosowski You might have to install gdb from the package manager. Then you would have to change the debugger in the Kit's settings.

Hi Thanks For your answer, It's Qt Creator, i use an external terminal. I used the Debbuger Log, but it closes when I close the application. Attached is the random error message that appears when I stop the application in debug mode and want to restart it. Thanks, VIncent [image: a29919e9-237b-470c-9f4e-1f3901ab9628.PNG]

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