Qt Creator and other tools

@dave2 said in How to automatically rename (many) data members?: is there a way to rename all data members in one go? I suppose Qt Creator does not support this, but perhaps another tool? I'm 80% sure the answer is "no". Your use-case is very niche. Doing this thousands of time would take days (weeks?), would be error-prone I'd say this is faster and less error-prone than creating your own automation tool. PS: Doing this change is not my decision, so no need to tell me how stupid you may think it is. Tell the decision-maker that it will take weeks. If they still don't change their mind, make sure they're paying you to do the job. And we are certainly not going to write a C++ parser ourselves... libclang makes this kinda feasible... ;)

Yes, I can reproduce with Creator 4.8.1 on Linux. I suggest you take a look at the bugtracker and see if something's known, otherwise please file as bug.

@SGaist said in qml caching problem: Check the content of the CONFIG variable and try CONFIG -= qtquickcompiler Ok, I didn't understand from the docs that the option is enabled by default! After disabling it, it created a new qml_qmlcache.qrc file (without override the original) and it seems to work in both debug and release mode.

does anybody know how this works?

@Alkaris said in Qt Creator keeping old files after deleting a project: it's already clear what I said in my post. Can't make it any more clearer than what I've already stated in my original post. You can definitely make it much clearer: Provide the "unrelated" error messages, verbatim. Provide the paths of the directories that you deleted. Provide the path of the Makefile that "shouldn't even be there". You can obfuscate your project name if you want, but show the directory structure. Why? For one thing, the information in your post was inaccurate: We know that if moc produces a file called moc_X.cpp, it will not produce a file called moc_X.h. Also, you could have: Told us how you installed Qt Creator Provide a screenshot on how you "right-click[ed] on Makefile and selected Open Directory Location" These are useful because the official version of Qt Creator doesn't show you the project Makefile, and doesn't have a menu item called "Open Directory Location". Your original post contained ambiguities that you didn't realize. The only people who would have understood your post 100% are people who can read your mind.

@emp1953 are you sure the Gui is not offscreen? I had this once, where I loaded the x,y from QSettings during startup and one time when I changed from dual to single monitor setup it would be moved offscreen, where the 2nd monitor would be.

Hi, Take a look at the QtSdkRepoChooser project.

Just follow the indications in the "Using Symbols from Shared Libraries" part.

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