Code completion got less helpful
-
I don't know what they did but code completion lost being helpful. When I type something I expect to see the absolute match on top. In the example below, why does QTextCursor snuggles in to the top? No one want's this. And this is only on example of many.
After repeatedly needing to remove false top offers I more and more break the habit to use the completer at all. Hope they'll fix this so it's usable again.
Or does anybody knows any setting to fix that?
Jazzco
-
The other broken part with code completion is the parameter hint. Earlier it tracked cursor movements so that the highlighted parameter changes when the cursor moves beyond a comma. Also the hint closed when leaving the braces. This highly makes sense because the UP and DOWN arrows are consumed by the hint to switch between overload.
In the following example hitting down doesn't move the cursor, need to hit ESC first:
I know it is high level whining but when things get worse step by step there's a point when it needs to be addressed to show it's not unrecognized.
-
I don't know what they did but code completion lost being helpful. When I type something I expect to see the absolute match on top. In the example below, why does QTextCursor snuggles in to the top? No one want's this. And this is only on example of many.
After repeatedly needing to remove false top offers I more and more break the habit to use the completer at all. Hope they'll fix this so it's usable again.
Or does anybody knows any setting to fix that?
Jazzco
Hi @jazzco2,
for the first problem, I think there was a patch recently that ranks matches that starts with the given text higher: https://codereview.qt-project.org/c/qt-creator/qt-creator/+/490803
Its not merged yet, but should hopefully appear in one of the next releases.
For the second problem, you might want to report an issue at bugreports.qt.io (don't forget to add a link to the report here).
Regards
