Details
-
Suggestion
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Description
User has reported that when he is trying to write QML code and the auto-completion appears with the results that are not optimal.
Example case:
User is trying to write "int" after property the editor proposes "onPa*int*edGeometryChanged" and not other options which would begin with "int" or "Int".
Maybe the proposed options order could propose options beginning with same string?
Example video attached.
Please notice in the video that there is an option for "*Int*validator" but the editor proposes first other options.