Qt Creator and other tools

@J-Hilk ahh, just leaving the cursor on the expression did the trick. I always double clicked it (complete word was marked) and hit F1 with the described effect. Thanks a lot!

@ChortleMortal Well I found out what the problem was. Since 6.2.1 was just released I thought I would make the static libraries for that. I did it exactly the way I did it before, and got exactly the same problem with the debug build. But then I noticed that the instruction at the end of the 'configure' operation had changed from before. Previously it said after the configure and build to run cmake --install . Now it says, run ninja install . I did that, and hey-presto the build works. Still incomprehensible why the new would differ from the old way. But I am moving on, now. Also, if anyone is having the same problem as myself, this is what I used to configure the system: configure -static -debug-and-release -no-pch -confirm-license -prefix "C:\Qt\6.2.1\static" -opensource -mp -nomake examples -nomake tests -no-icu -no-opengl -no-openssl -skip qtwayland -skip qtquick3d -skip qtquickcontrols2 -skip qtquicktimeline -skip qtshadertools -skip qtdeclarative -skip qttools -skip qtdoc -skip qttranslations -skip qt3d -skip qt5compat -skip qtcharts -skip qtcoap -skip qtdatavis3d -skip qtlottie -skip qtmqtt -skip qtopcua -skip qtscxml -skip qtvirtualkeyboard -skip qtmultimedia -skip qtwebengine -skip qtwebview

@Mark81 said in Cannot rename directory in QtCreator: inside the IDE Please be aware that you're not obliged to use Qt Creator IDE to develop (write/test/debug) any Qt application...

I think that the problem is not specifically bound to a Windows install, as I've encountered it under both Windows and Linux. The symptoms are always the same: the compilers are detected correctly but corresponding kits either have no compiler specified or have wrong compiler set, and I'm unable to fix it as they are autodetected kits, so the option to select compiler is unavailable. The only workaround I've found is to duplicate failed kits and set the compiler in the duplicate. The workaround produces valid kits, but the kit selection becomes quite messy, as almost for each working kit we have a failed one, and I have to always keep in mind which one is which. An option of selecting a compiler for an autodetected kit manually would solve the issue. If the Qt developers want to keep the idea of "autodetected means set automatically", a possible solution would be to add a "reset to autodetected" button, but for the case when autodetection fails the option of editing kit manually is, IMO, a better solution than creation of a duplicate. [image: 696ad952-6002-481d-bc8a-19fabf5af83a.png] [image: 61babf38-8df3-4d99-861c-f6ee390d189b.png]

the solution was to pass --pdb into windeployqt. I had copied the qt libs into my exe dir, but not their corresponding pdb files.

@mrjj said in What information will be collected and uploaded for online installer?: Hi https://www.qt.io/terms-conditions/#privacy By default, there is no data collection in Qt tools. Its an opt-in. I'm not very sure about this, for linux login is not mandatory.

Hi, It depends, are you talking about PySide2/6 or PyQt5/6 ?

@Omprakash-sharma I guess you're talking about Windows? Step by step: Download Qt Online Installer Start the installer Select Qt for Min GW Select MinGW under Tools Install If something is not working please provide more information!

Hi, How are you using that library ? Please show your .pro file.

@_iterates I never used Qt Vs Tools, but in QtCreator <ou have to specify the while path to qmake.exe, including file name. Maybe it is same in Qt Vs Tools?

Hi, One issue here is that your anaconda installed software is trying to use part your system installed Qt. I would say that the packaging of ParaView is wrong. At the very least the Qt version provided with it looks incomplete.

Hi Siddhartha, I am facing a similar issue, have you figured this out? If yes, then could you please help, thanks in advance.

I know it's been a while over this topic but as a reference to newer searchers: You can just disable those warnings and errors in coding time. And only at compile time you can receive them. For this : Tools -> Analyzer -> Clang Tools and uncheck "Analyze open files" option button. After that you will have a clear coding screen : ) Regards

Is there any resolution to the Unsupported media type issue? It appears the camera is returning a list of pixel formats and it doesn't like the YUY2 {32595559-0000-0010-8000-00AA00389B71} and Motion JPEG {47504A4D-0000-0010-8000-00AA00389B71} formats. I'm still trying to wrap my head around how to do camera configurations, and looking at the code in dscamerasession.cpp it doesn't look like there's much one can do to fix this issue but I haven't dug too deep in yet. I should note that the camera is working correctly, but the terminal is full of these messages when I hit QCamera::load() function, so I guess I'm just wondering if there's a way to hint to the camera class to ignore these formats ahead of time. Appears this works just fine in QT6 and QT5 doesn't support recording video anyway :P

@IknowQT said in Make .pro file Not working Object reference not set to an instance of an object: Is there any way to manually create a .pro file? Of course. It's just a text file. You can create a pro file by calling qmake with -project parameter. But you will most probably need to edit the generated file. See for more details: https://doc.qt.io/qt-5/qmake-project-files.html