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

Bug 269426

Summary:	[FieldAssist] Autocomplete and combo conflicts
Product:	[Eclipse Project] Platform	Reporter:	Susan McCourt <susan>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Susan McCourt

2009-03-19 13:55:25 EDT

When an AutoCompleteField is put on a Combo, there are annoying autoactivations that occur and shouldn't.  If the user is trying to scroll through the combo contents, the auto complete activates for each selection in the combo.

I worked around this in p2 with ComboAutoCompleteField.

I originally wanted a hook to prevent autoactivate, but there is not one.  There is a hook for openProposalPopup() but autocomplete doesn't call this method.

Instead, I hooked into the proposal provider to propose no matches when the text typed is already an exact match with a single proposal.  (kind of like an auto-accept).  I'm not sure this is the right general answer.

Comment 1 Susan McCourt

2009-09-30 14:12:27 EDT

This sounds a lot like bug 202937, which fixed a similar problem, but there must be some scenario where it still happens.  I can't reproduce it in the FieldAssistTestDialog, and when I commented out the workaround code in p2 that was preventing the problem (by not proposing anything when there's only one match) I still don't see the problem.

I do remember seeing it at the time, but can't reproduce it now.

Comment 2 Eclipse Webmaster

2019-09-06 16:15:14 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 3 Eclipse Genie

2021-08-27 13:20:54 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.