Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autocomplete is inaccurate due to alphabetical sorting of suggestions #21726

Closed
KoBeWi opened this issue Sep 3, 2018 · 6 comments
Closed

Autocomplete is inaccurate due to alphabetical sorting of suggestions #21726

KoBeWi opened this issue Sep 3, 2018 · 6 comments

Comments

@KoBeWi
Copy link
Member

KoBeWi commented Sep 3, 2018

Basically this:
image
I wanted to autocomplete Vector3, but writing Vec3 suggests me PoolVector3Array. This happens when you write letters in different order (in example above I'm skipping "tor"). Autocomplete ignores how you started writing a word and sorts everything alphabetically. I'd expect it to actually select Vector3 in above case.

Another example:
image
Actually for this one writing "minf" would work, but still, autocomplete could better predict what I'd like to write. I doubt anyone would start RemoteTransform this way.

Tested in 3.1 alpha.

For comparison, here are VS Code results for these completions:
image
image
(btw, see how VS Code highlights actual written letters, rather than just the beginning of the suggested words like it is in Godot. But I suppose I could create separate issue for that)

@rokasv
Copy link

rokasv commented Mar 9, 2019

Vec3 into PoolVector3Array is excruciatingly painful (still in 3,1 RC1)

@KoBeWi
Copy link
Member Author

KoBeWi commented Mar 9, 2019

Yeah, the linked PR fixes it, but adds some more stuff that made it too big, so it's not merged yet :/

@rokasv
Copy link

rokasv commented Jan 29, 2020

Just realized this is not marked as a bug.
That's a shame, since the code editor and export features are the only thing I use in the engine. 😞

@me2beats
Copy link

Still in 3.2.3
Why not a bug tho?

needless results
needless2

As you can see, completion suggests superfluous results.

this is quite annoying and slows down the scripting.

@Calinou
Copy link
Member

Calinou commented Feb 13, 2021

Why not a bug tho?

It's working in a less than ideal manner, but it's technically working as intended. Please don't pressure contributors to label everything as a bug 🙂
Otherwise, we might as well not have bug and enhancement labels…

@KoBeWi
Copy link
Member Author

KoBeWi commented Mar 8, 2022

Closing in favor of this proposal: godotengine/godot-proposals#4189

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants