Re:Autocomplete as an Interface (2015)
by seanmcdirmid on Thursday January 16, 2020 @10:59AM
(#22065714)
I find that the timing is actually worse, because then I start waiting for the menu to appear as affirmation for some assumption I made about the namespace. It’s also jarring that it appears out of sync with keystrokes. Turning off the delay and working on menu placement instead could provide for better PX, but it is something that can be user tested a lot, at least.
[ Parent
| on HN ]
Re:Autocomplete as an Interface (2015)
by jasonlotito on Thursday January 16, 2020 @11:15AM
(#22065894)
> I find that the timing is actually worse
That's fine. Amazingly, these things are customizable to fit everyones needs. Thinking there is only one way to do it is silly, but apparently a number of developers things autocomplete can be done only one way.
Re:Autocomplete as an Interface (2015)
by seanmcdirmid on Thursday January 16, 2020 @11:47AM
(#22066233)
They aren’t really customizable that much. I don’t think there is a property in VS or VS Code to haggle with to reduce autocomplete timing to zero, and it still doesn’t deal with it being too intrusive to be used continuously. Each design decision has a cascading consequence, making customization very difficult.
Happily, there are some settings like that. https://code.visualstudio.com/docs/editor/intellisense
``` // Controls the delay in ms after which quick suggestions will show up. "editor.quickSuggestionsDelay": 10, ```
Re:Autocomplete as an Interface (2015)
by seanmcdirmid on Thursday January 16, 2020 @08:10PM
(#22070881)
Neat! I've actually never had a problem with the delay in VS Code, and 10ms is basically the way I like it anyways (immediate).
Some people might still be annoyed by the code completion menu placement, which isn't configurable (yet).