It’s extremly annoying not being able to write the number 1 and press enter without being bullied by the auto-fill.
I really like the auto fill but please don’t do it on numbers.
A shortcut would be great. I’m used to pressing Ctrl+Space to bring up autocomplete. Popping up automatically is obnoxious.
7 Likes
Why is enter still what selects it?
I’d hate that… It’s unintuitive. The only reason I use autocomplete is because it shows automatically, I might as well just type out the whole thing rather than think “Have I used this before? Maybe I have, let me press Ctrl + Space and then check and press enter if it’s there” It’s pretty good as-is, I just don’t know what the shortcut is to cancel it, for example when I’m writing “do” (enter) and I’ve got another variable with “do” at the start, it’ll be overwritten.
1 Like
Escape. Way out of the way.
1 Like
Thanks, I’m sure I tried that and it didn’t work before - will see next time I’m in studio.
Wondering the same thing. I don’t know if there’s better key for selecting the autocomplete, but I don’t like the enter key being it. When I type ‘do’ for a loop, the autocomplete pops up and when I press enter to make a new line it inserts the autocomplete in place of do, then I have to retype do then click on the next line or press an arrow to move down, it’s really frustrating.
The standard is usually tab, which also works in studio. The problem here more than likely lies in the Return key being a universal selector, whereas it should not be universal, but have some form of a whitelist.
Same here. I think it popping up to show u variables/functions can be useful enough but pressing enter to select it is a bit strange.
While true docamspin
Yeah, normally I love to have Intellisense on, but with the latest changes I’ve had to turn it off because these issues are disrupting my workflow. Enter definitely shouldn’t be the selector for autocomplete.
the problem is that instead of matching from the beginning it tries to find throughout the variable name. thats counterintuitive i dont type from the middle of the variable name then go back and type the beginning. it should only match from the beginning of variable names.
similarly i dont think you can directly create variable names with numbers in the beginning anyway or you’ll get some malformed number error, so im not sure why it would suggest for numbers at all.
edit: i know someone will say it so ill added it on, yes i know you can do getfenv()[“1hey”]=true but no person does this practically, they use it for highly specialized use cases so its not valid in everyday scenarios. if you want to inject variables into the environment to get around a roblox limitation in the first place then thats your thing and intellisense shouldn’t support it for variable completion because you’re indexing the environment as a table maybe in the future when intellisense supports table key autocompleition that’d be nice.
Imagine you have a function named drawCircle and you can’t remember whether it’s named drawCircle, createCircle, newCircle, etc. Matching from within the word can be useful if you remember key words in the variable name but not necessarily the beginning. Matching part-way through a word wouldn’t normally be a problem since you could just ignore the prompt if you weren’t looking to autocomplete – the only reason it’s become annoying is because enter autocompletes the word (which it shouldn’t).
then it should do it like visual studio:
show the most relevant results first from the beginning of the word, then show possible results regardless of placement below the relevant results.
quite frankly the current matching system is anything but proper. no other respected IDE that i know of does this (doesn’t mean there isn’t one, though).
IMO, that edge case is not worth the mess that comes from not using the beginning of variable names. Like @FriendlyBiscuit said, I cannot think of an IDE that does it this way. It’s for good reason too.
agreed with @Osyris and @FriendlyBiscuit i can’t ever think of a situation where i was sat writing code and thought to myself ‘I forget whether it was createCircle, newCircle or drawCircle, you know?’
That “edge case” can be properly managed as FriendlyBiscuit mentioned. Implemented properly it’s definitely worth it.
In large projects this is frequent. In small ~2,000 line games you don’t run into this issue often.
ill agree i like friendly’s compromise though
you mean the supermajority of roblox games?
It’d be one thing if searching through variable names part-way would take the amount of effort it’d require to implement auto-collapsing panes for Studio. Its small window of use would drop the priority beneath the point of consideration because it wouldn’t be worth that much effort to implement. But it’s not at that level. It’s a small gimmick that already has a functioning algorithm – all that’s left is a UI change if we’re going with what FriendlyBiscuit suggested. The feature wouldn’t be used on a large scale, but it also doesn’t require a significant amount of work to implement. low+low makes it reasonable to consider implementing.
which i agree with as stated previously.
i just dont think its important and needs to be there because the use cases are so small, but since it is such a minor feature anyway the effort required doesn’t outweigh the small benefit from it.
I think the real issue, besides the fact that it triggers on keywords, is that it triggers on words that just contains the letters ur typing.
speed = 0
lastspeed = 1
lastspeed = speed --Now it will force me to write lastspeed if I press enter.
Only trigger when the word begins right.