Consider popping up the content assist dialog automatically after a user presses '.' #63

Closed
aeisenberg opened this Issue Dec 14, 2012 · 4 comments

Projects

None yet

2 participants

@aeisenberg
Contributor

No description provided.

@aeisenberg
Contributor

Would need to include a (configurable) delay.

@cawoodm
cawoodm commented Dec 14, 2012

Why? If you're quick you just type past the suggestions. They should be non-intrusive.

@aeisenberg aeisenberg was assigned Jan 24, 2013
@aeisenberg
Contributor

Having a look at this now.

@aeisenberg
Contributor

Depending on content type, we should have different keys bring up content assist. Eg- html should do it on '<' and css should do it on '#' and '.', etc.

@aeisenberg aeisenberg added a commit that closed this issue Jan 24, 2013
@aeisenberg aeisenberg Auto activate content assist on '.' fixed #63
This is now implemented, with the following notes:

1. Content assist will only be auto activated in .js files
2. We should consider making this configurable and using a notion of content types (see #147
3. auto activation defaults to 500ms
4. auto activation can be configured using the ui.auto_activation configuration in .scripted.
5. I changed auto activation for the drop-down menus to use this property as well.
378728b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment