Qt Creator and other tools

@kshegunov said in Is it possible to disable C++ "Semantic Issue" warnings when working on a C project?: Look up Tools > Options > C++ > Code model

@Galbarad so please move this topic to SOLVED state. Strange behavior, nevertheless.

Hi, That's a pretty good question. I wold recommend bringing it to the interest mailing list. You'll find there qdoc developers/maintainers. This forum is more user oriented.

@dave2 for completeness sake, I tested it with MacOS & Clang + LLDB, doesn't work at all there as well

created new bug, as clipboard bug is only tangentially related

@JealousFish Yes, In Qt Creator is called “Build Directory”, where file .o are created and where you find your application. In the past I had the same issue, when I deleted the build folder the problem disappeared. Sometimes, when compiler failed and the code seems ok, I delete the builder folder and the problem disappears. I think, but it is only my idea, when this happens some files .o are locked, perhaps because I stopped the previous compile.

@JonB said in how to sort errors (issues panel) by file?: Maybe compilers are female then.... Haha, made my day. Just as example: completely compiling QtCreator on my personal notebook takes approx. 25 minutes with 6 to 8 cores. One more or less does not matter. However, with only 1 core it would take over two hours. So when dealing with large C++ projectes, multicores are a must. Really.

Solution found. Through JS implementation to template file. Something like this: %{JS: var time = new Date(); time.getHours() + ":" + time.getMinutes() + ":" + time.getSeconds(); }

Although it may not be why you are getting the problem, I believe you would be better off pointing at a msvc2017_64 folder if you are using VS 2017. Another issue is that the Win32 version is pointing at the *_64 folder, though unless you're running such a build I don't think this will cause a problem. I am surprised you have a UicDir without a MocDir in the vcxproj and that the lupdateOnBuild also doesn't show up. It looks like the VS ui and the xml aren't synced up. Also, make sure that you have the version coded in for every vcxproj file that uses qt.

See https://bugreports.qt.io/browse/QTIFW-671 and vote and comment there.

SpellChecker 1.2.0 works great on macOS Sierra with Qt Creator 4.6 and Hunspell 1.7.0. http://pankdm.github.io/hunspell.html brew install hunspell and may require sudo ln -s /usr/local/lib/libhunspell-1.7.dylib /usr/local/lib/libhunspell.dylib sudo ln -sf /usr/local/lib/libhunspell-1.7.a /usr/local/lib/libhunspell.a SpellChecker 1.2.0 compiled from source https://github.com/CJCombrink/SpellChecker-Plugin/releases with Qt Creator 4.6. /Users/myuser/Documents/qtc/qt-creator-opensource-src-4.6.0/src/plugins/plugins.pro SUBDIRS = \ spellchecker \ ... /Users/myuser/Documents/qtc/qt-creator-opensource-src-4.6.0/src/plugins/spellchecker/spellchecker_local_paths.pri LOCAL_QTCREATOR_SOURCES=/Users/myuser/Documents/qtc/qt-creator-opensource-src-4.6.0 unix { Debug :LOCAL_IDE_BUILD_TREE=/Users/myuser/Documents/qtc/build-qtcreator-Desktop_Qt_5_10_1_clang_64bit-Debug Release:LOCAL_IDE_BUILD_TREE=/Users/myuser/Documents/qtc/build-qtcreator-Desktop_Qt_5_10_1_clang_64bit-Release LOCAL_HUNSPELL_LIB_DIR=/usr/local/lib LOCAL_HUNSPELL_SRC_DIR=/usr/local/include } Plan to test with Qt Creator 4.8. Thanks!

That's QTCREATORBUG-21873 now.

@CP71 said in Drag and drop between two instances of QtCreator: @Mark81 Have you tried with copy and paste in the Designer? Copy and paste works. But it's a different thing. As you know, you cannot paste into an existing layout. In such a case the drag and drop is the only way we have to add a widget without breaking the layout.

@aha_1980 Fine. Thank you.

@davecotter said in errors that aren't? or: diff btwn "solid red dot" error and "hollow red dot" error?: how does one turn off the clang code model? i looked and don't see it See @kshegunov's link

I tried to downgrade to 5.11 and same result so I suspect it's not a Qt bug but something in my code

@aha_1980 said in can't find dll when debug/run in QtCreator: @jronald No. Once you changed the PATH for a project in Creator, the systems PATH no longer applies to this project, i.e. any change to the systems PATH have no effect for that project. ok, sophisticated.