Qt Creator and other tools

I was diverted from this for a while, but coming back to it and trying it again, it is clear that I was incorrect in saying that 5.9.6 is no longer available via the installer. I suspect I missed ticking the box that provides access to archive versions of Qt. I suppose I have not needed to do this in the past as 5.9.6 was still available as a non-archive release.

@natxo14 said in Qt Creator Occurrences Text Highlight not working for non cpp files: I've been searching in Tools->Options->Text Editor 'Fonts and Colors' and 'Generic Highlighter' tabs, but couldn't find where the cpp files are told to be treated differently from other file types. They're not, there's a code analyzer only for c++ (and a partial support for qmake autocompletion).

Have you enabled setting "Save all files before build" from Settings->Build&Run->General? If yes and it does not work, then I'd say it's a bug in Qt Creator, please report it.

my problem was somthing like you. I solved it by removing all the manual setting(I mean the manual sdk, ndk and openssl addresses) then I first give the address of jdk 1.8 and click on set up SDK in the following picture: [image: f4d1c37f-5085-4592-8560-0b96662e4935.png] Qt creator automatically make it.

@nsourl said in Qt Design Studio 2.0 - Linux Mint 19.3 glibc error: glibc version is 2.27 GLIBC_2.28' not found You can't use it with the version you have installed

I have the same problem. Did you solve this?

@mrjj Thanks appreciate all - especially the add to format current file. Doing it Qt way gets tiresome... [image: e06da6a2-206b-498b-9a6e-e5cabc201702.png] Just because I tried to add some text to "documentation" but it won't take anything. It gets little hard to reply and implement it , so I'll get back to you when I get it all put together. As another matter - since you mentioned brackets I like to cut and paste - there is a trick to put mouse behind starting bracket and "select until next bracket " . I have been looking for similar to actually select between #iifdef .. #endif . I know the Qt editor puts different background color to show the #ifdef... #endif but I like to copy such range.

No-one else has a solution for this?

I also have QTableWidgets inside tabs of a QTabWidget and have had this problem for a long time. Every time the .ui file is saved in QtCreator it sets the horizontal headers of all my tables to invisible except for the first table.

Hi and welcome to devnet, You're not showing enough of the build log to identify the error you have.

I found this Creating Run Configurations for Subprojects To prevent Qt Creator from automatically creating run configurations for SUBDIRS projects, specify the following variable in the .pro file of the SUBDIRS project: CONFIG += qtc_runnable. Qt Creator creates run configurations only for subprojects that also have CONFIG += qtc_runnable set in their .pro files. However, after using the "big icon" adding CONFIG to both SUBDIR .pro and the project I want to run I still run the project selected by the icon. How do I "clear" the "icon" selection to test the CONFIG? ADDENDUM, let me say this - it somebody can point me to "purpose of the LEFT big icons" documentation I am game. It appears to be a "cute GUI" afterthought / replacement for "F1" help. ( There seems to be some relations to plain "options"... ) I find it "interesting" how SUB_DIRS options are so scattered throughout Qt documentation. qmake docs covers how to setup sequence of its works , but one have to use "big icons" to find out how to actually select which SUB_DIRS project. to execute. There is something missing in philosophy of SUB_DIRS here. And in the process discovering "dependencies" .... ( next project - how to verify that these options are actually working ...) Personally - I would prefer all these "big icons " options to be part of the standard window style menu driven scheme.

@SGaist I would have thought something like qmlimportscanner would be important to build an application, but perhaps I am wrong. Yes, it makes sense that designer would not be there.

I got it thank you!

@SuperJarvisCN This is not the right place to report bugs. Use Qt bug tracker for this.

This is not a lot information to go on. That makes it quite hard to help you with your problem. I suggest you share what you have (main.cpp and CMakeLists.txt) so that others can try out if they can replicate your problem.

Hello, i started to have the same warning after i had updated MSVC 2019 Compilers. I corrected this issue by re-detecting compilers list. Go to "Tools/Options/Kits" [image: 1e61b417-f284-425c-9fd7-aff5568a0698.png] then you can remove the "Emscripten Compiler" which is the one causing this warning.

Thanks very much again - that has solved it for me. my version was buried deep - but I did find it eventually .