5 ms·
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’
by seanmcdirmid 7y ago
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.
- jasonlotito 7y ago> 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.
- seanmcdirmid 7y agoThey 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.
- fbartho 7y agoHappily, there are some settings like that. https://code.visualstudio.com/docs/editor/intellisense https://code.visualstudio.com/docs/editor/intellisense ``` // Controls the delay in ms after which quick suggestions will show up. "editor.quickSuggestionsDelay": 10, ```
- seanmcdirmid 7y agoNeat! 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).