Description Sebastian Zarnekow 2011-05-10 12:20:32 EDT

The jface framework uses ITextHover#getHoverRegion to determine region information that will be passed to ITextHoverExtension2#getHoverInfo2 in an own thread to make sure the ui is not blocked. Xtext's hover implementation uses #getHoverInfo2 to compute the result of #getHoverRegion which renders the framework's optimization strategy pointless. Even worse, the expensive computation of the actual hover data is performed twice, once in the ui thread and once in the computation thread.

For indigo, we can implement a workaround to reuse the computed information when #getHoverInfo2 is actually called from the computation thread, but we should really try to fix as it makes it really hard to compute quickfixes that are not trivial, e.g. for broken links to constructors or classes.