Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326435 - "Greedy" Content Assist
Summary: "Greedy" Content Assist
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-28 11:52 EDT by Christoph Zwicker CLA
Modified: 2017-09-19 17:12 EDT (History)
1 user (show)

See Also:
sven.efftinge: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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