Why has autocompletion in Qt Creator gotten worse?
-
I am just getting back into Qt programming (using Qt 6.3 & Qt Creator 7.0.2 on Windows 10 Pro) after have been away from it for a few years. I am surprised that the autocompletion in Qt Creator is not as good as I remember it to be (I think I was previously using Qt 5.1, but I'm not sure). I noticed that:
-
Previously when I typed a period, Qt Creator always knew when it needed to be replaced with "->". Now it often gets it wrong.
-
Previously when adding a new method to a class, Qt Creator would use the declaration I had just added to the header file to automatically fill in the arguments. Now it never does it.
-
Previously when adding a connect() call, Qt Creator would offer autocompletion for the SIGNAL() and SLOT() calls. Now it never does.
I would think that when updating Qt Creator one of the requirements would be to make sure to not make it less user friendly. Is there some way I can configure Qt Creator 7 to get the autocompletion to work as well as it used to?
-
-
Hi @CodeCat, these are valid concerns. Can you please add them to https://bugreports.qt.io/browse/QTCREATORBUG-26959, and check if the issues mentioned in that bug report affects you too?
-
I am just getting back into Qt programming (using Qt 6.3 & Qt Creator 7.0.2 on Windows 10 Pro) after have been away from it for a few years. I am surprised that the autocompletion in Qt Creator is not as good as I remember it to be (I think I was previously using Qt 5.1, but I'm not sure). I noticed that:
-
Previously when I typed a period, Qt Creator always knew when it needed to be replaced with "->". Now it often gets it wrong.
-
Previously when adding a new method to a class, Qt Creator would use the declaration I had just added to the header file to automatically fill in the arguments. Now it never does it.
-
Previously when adding a connect() call, Qt Creator would offer autocompletion for the SIGNAL() and SLOT() calls. Now it never does.
I would think that when updating Qt Creator one of the requirements would be to make sure to not make it less user friendly. Is there some way I can configure Qt Creator 7 to get the autocompletion to work as well as it used to?
sounds to me like exclusive clang code model issues try disabling it:
but you'll loose c++14/17 and newer feature detections inside your files and those my falsely be detected as errors.
alternatively use QtCreator 5.0.3 (the one I use) fore some unexplicit reason, this version runs much, much better with the clang code model than any other, later one.
https://download.qt.io/official_releases/qtcreator/5.0/5.0.3/
-
-
I am just getting back into Qt programming (using Qt 6.3 & Qt Creator 7.0.2 on Windows 10 Pro) after have been away from it for a few years. I am surprised that the autocompletion in Qt Creator is not as good as I remember it to be (I think I was previously using Qt 5.1, but I'm not sure). I noticed that:
-
Previously when I typed a period, Qt Creator always knew when it needed to be replaced with "->". Now it often gets it wrong.
-
Previously when adding a new method to a class, Qt Creator would use the declaration I had just added to the header file to automatically fill in the arguments. Now it never does it.
-
Previously when adding a connect() call, Qt Creator would offer autocompletion for the SIGNAL() and SLOT() calls. Now it never does.
I would think that when updating Qt Creator one of the requirements would be to make sure to not make it less user friendly. Is there some way I can configure Qt Creator 7 to get the autocompletion to work as well as it used to?
@CodeCat said in Why has autocompletion in Qt Creator gotten worse?:
Previously when adding a connect() call, Qt Creator would offer autocompletion for the SIGNAL() and SLOT() calls. Now it never does.
Your other concerns are valid. As @J-Hilk says, I hear nothing but problems with Creator 7....
But the
SIGNAL/SLOT()one is not, insofar as you would be much better off not using such macros. For your own good, change over to New Signal Slot Syntax :) -
-
I had to work on an old laptop (2-core Sandy Bridge CPU) for the past 3 months instead of my Ryzen 7 desktop PC, and I've noticed that code indexing and auto-completion is incredibly slow in Creator 7, and much much better in Creator 5 on the same laptop. With no visible differences in functionality.
