Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Very slow autocompletion work #1814

Closed
Aguinore opened this issue Jul 28, 2016 · 1 comment
Closed

Very slow autocompletion work #1814

Aguinore opened this issue Jul 28, 2016 · 1 comment

Comments

@Aguinore
Copy link

Aguinore commented Jul 28, 2016

Hi!

Eclipse Ceylon IDE freezes for a while after typing . and pressing ctrl+space for autocompletition. It would be not so bad if I could continue typing, but IDE prevents it until completition computing will be done which might take up to 30-40 seconds on my i7 desktop.

@davidfestal davidfestal self-assigned this Jul 28, 2016
@davidfestal davidfestal added this to the 1.2.3 milestone Jul 28, 2016
davidfestal pushed a commit that referenced this issue Sep 12, 2016
For #1589 (Run the "Preparing completions" task in a background thread)

Fixes also:
- #1814 : Very slow auto-completion work
- #1815 : Double dots

There were 2 main problems:

- the UI was frozen because we had to construct completions in another
thread, and run the `Display` event loop manually while waiting for the
result.
Doing this now allows registering a document-change listener that
cancels the completion search as soon as some new text is typed in the
editor.

- the images should not be retrieved during the completion construction
(this can causes a dead-lock), but lazily when
`CompletionProposal.getImage()` is called.

Additionally, this commit also enables retrieving partial fast
completion results when in auto-activation mode, or when a build is
running. Each time a partial completion result is returned, a warning is
shown in the status bar.
@davidfestal
Copy link
Contributor

Fixed

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

No branches or pull requests

2 participants