Qt Creator and other tools

okay so "contains" is not a substring containment test. the test must be for the entire text of the variable. so this worked: if (contains(TARGET, "kJams Lite Debug") | contains(TARGET, "kJams Lite")) { message("KJAMS_PRO NOT set :(") } else { message("KJAMS_PRO SET! :)") DEFINES += KJAMS_PRO }

When NSJsonConvert is being compiled, the compiled does not have QJsonObject header included. Do you build using qmake? Can we see the .pro file?

On Windows, the QtCreator.ini file is located: C:\Users\username\AppData\Roaming\QtProject\QtCreator.ini Look for: FindInFiles\filters= AllProjectsFind\filters= Success when removing badly formed file patterns entries on Qt Creator 4.3.1.

I believe this is a bug in Qt Creator so I filed a bug report about this issue: https://bugreports.qt.io/browse/QTCREATORBUG-18666

I've soled in this way: sudo -i gedit /etc/environment Next add: QT_AUTO_SCREEN_SCALE_FACTOR=1, saved and restart my pc. Also QT_DEVICE_PIXEL_RATIO=2, works with QT editor 3.5.1 :)

You can check the existing types here https://github.com/qt-labs/vstools/blob/dev/src/qtvisualizer/qt5.natvis It would be nice, to have that for every single type in Qt, since by default it doesnt show any valueable information, mostly just raw pointers to the object. One example could be every Json-related type (http://doc.qt.io/qt-5/json.html)

I have the same problem here with Visual Studio 2017 (15.2) There is already a bug report in JIRA: https://bugreports.qt.io/browse/QTVSADDINBUG-463

OMG is it that easy? where's the "d'oh!" emoji?

"debugging for QJSEngine. The intention is to have a design that allows developers to write scriptable applications where scripts run in other threads, not the Qt GUI thread, so they could be debugged using dedicated Qt APIs. But this, again, is a quite distant possibility, no concrete plans for that." Current roadmap of Qt ((

Hi, If you want to build your documentation following Qt's style then qdoc is the way to go.

@davecotter I understand what you mean, I just want to point out that you should use correct wording. If you know what debugger is used you can, for example, check whether there are any known issues like yours here: https://bugreports.qt.io/projects/QTCREATORBUG/issues/QTCREATORBUG-18608?filter=allopenissues If not you can file a bug there.

You should get a stack trace to see what it is about.

You should rather clean the permissions from that file than run Qt Creator with sudo.

Hi It seems to be here. \src\plugins\qtsupport\baseqtversion.cpp" LINE 1336 QList<Task> BaseQtVersion::reportIssuesImpl(const QString &proFile, const QString &buildDir) const { ... QString sourcePath = QFileInfo(proFile).absolutePath(); const QChar slash = QLatin1Char('/'); if (!sourcePath.endsWith(slash)) sourcePath.append(slash); if (tmpBuildDir.count(slash) != sourcePath.count(slash)) { const QString msg = QCoreApplication::translate("QmakeProjectManager::QtVersion", "The build directory needs to be at the same level as the source directory."); results.append(Task(Task::Warning, msg, FileName(), -1, ProjectExplorer::Constants::TASK_CATEGORY_BUILDSYSTEM)); } return results; }