Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326435

Summary: "Greedy" Content Assist
Product: [Modeling] TMF Reporter: Christoph Zwicker <zwc>
Component: XtextAssignee: Project Inbox <tmf.xtext-inbox>
Status: CLOSED FIXED QA Contact:
Severity: minor    
Priority: P3 CC: sven.efftinge
Version: unspecifiedFlags: sven.efftinge: indigo+
Target Milestone: M6   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Christoph Zwicker CLA 2010-09-28 11:52:42 EDT
Build Identifier: 20100917-0705

Already reported and confirmed in the TMF Forum (http://www.eclipse.org/forums/index.php?t=msg&th=197441&start=0&S=5519c938277910fc256c3c3863908dac):

Hi,

I have a problem with the behavior of the content assist handler provided in the org.eclipse.xtext.ui plugin. The "activeWhen" element only checks for activeEditor, which stays set (I believe) even when another part is activated (which may also provide content assist). Due to this, the command is handled by org.eclipse.xtext.ui.editor.handler.ContentAssistHandler and org.eclipse.jface.fieldassist.ContentProposalAdapter does not get a shot at the event (at least that's what I figure from a 30' read through the sources).

Is there a reason why the handler is not activated only when the editor is "really" active?

Thanks,
Chris

Reproducible: Always
Comment 1 Sven Efftinge CLA 2011-03-26 20:31:39 EDT
That was fixed in M6
Comment 2 Karsten Thoms CLA 2017-09-19 17:01:18 EDT
Closing all bugs that were set to RESOLVED before Neon.0
Comment 3 Karsten Thoms CLA 2017-09-19 17:12:41 EDT
Closing all bugs that were set to RESOLVED before Neon.0