Qt Creator and other tools

@TheTobruk you may want to take a look at this document.

@Robert-Hairgrove I had a Déjà-vu when I read the bugreport :)

I still have the issue with QtCreator 4.7.0. This is boring when the assert comes from Qt. At least using qInstallMessageHandler works fine. Windows 10, with Mingw and Qt 5.10.1

@TheTobruk said in How do SIGNAL or SLOT know which object I am referring to in a connect function?: connect(ui->horizontalSlider, SIGNAL(valueChanged(int)), ui->progressBar, SLOT(setValue(int))); SIGNAL() / SLOT() are macros which return a char*, which is then used by Qt (MOC) for static lookup in a list. So the (cleaned up) method name is searched in the meta-object of the object you passed in the parameter before. You may also checkout the new signa/slot syntax (introduced with Qt5), which also accepts function pointers. The old syntax is basically the same, but the "dereferencing" of the function is done each time during runtime and also string based. connect(ui->horizontalSlider, SIGNAL(ui->horizontalSlider->valueChanged(int)), ui->progressBar, SLOT(ui->progressBar->setValue(int))); following your thinking this would actually call the method, which isn't intented.

In general as for all applications it would be through QSettings on windows. For addElevatedOperation you would need to write your application or to use a command line based regedit

I am so dumb :D

@kkoehne Ah, OK you are right. It is limited to release mode. When switching to debug and rerun qmake it is gone. The only solution would be to have different diagnostic configurations per kit. At the moment I have added "-Wno-zero-as-null-pointer-constant" to a copy of the built-in settings. This solves the problem with the warning at the time being.

Ok thanks :)

@PbvS said in Clang Code Model - QtCreator 4.6.1 vs 4.7.0: I'm using cmake. Ok, I'm out here... Tried using add_definitions("-std=c++14") as well as set(CMAKE_CXX_FLAGS "-std=c++14"). Found on the internet also another approach using add_compile_options(-std=c++14) but also no luck. The flags needs to be passed to the Code Model - no idea how this works for Cmake. You might also ask this question on the Creator mailing list... Regards

Hi @KRP1, Please have a look at: https://bugreports.qt.io/browse/QTCREATORBUG-20829 which might be related.

@koahnig said in Creator: Possible to switch back to old model for autocomplete only?: @Asperamanca Did you check out already under "Tools"->"Options"->"{}C++" and tab "Code model". There are a couple of different settings possible. Just came across this. Thanks for pointing that out. I don't think these settings are related to the autocomplete behavior.

@BSDUser said in Modularized QT application - my program can't find .so files: The problem I have is I can't start the main binary, because the program loader can't find file1.so and file2.so even if they are in the same directory as the main program. On Windows it would work that way, but Unix explicitely forbidds loading libraries from the working directory - for security resaon. You can however, force the linker to load them anyway, e.g. by modifying LD_LIBRARY_PATH. So the question is, how to install an output files (.so) into /usr/lib directory? My very first idea was to call make install as an extra build step, but it needs root. Correct, but for testing that's not needed. Creator automatically extends LD_LIBRAY_PATH if the linker options are correctly set. So can you please show your projects .pro file? Regards

Ok thanks :)

Ok, here's is the full error message, as posted in a message box: "Error while saving file: Cannot write file <Absolute file path>: Unable to remove the file to be replaced" In this particular case a .cpp file when I manually tried to save it. File is still marked as unsaved. On second try, saving works.

Wait, do you mean that Qt Creator 4.6 works on your system and in a container bug not Qt Creator 4.7 ?

Actually I have just realised that I am running the QTC in ~/Qt/Tools (which I am guessing came with the 5.11 d/l) Ta.