Bug 213035 - [Commands] ContentAssistCommandAdapter without key binding on application startup
Summary: [Commands] ContentAssistCommandAdapter without key binding on application sta...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-14 10:51 EST by Gerhard Schaber CLA
Modified: 2019-09-06 15:32 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Schaber CLA 2007-12-14 10:51:02 EST
Build ID: v200712060500

Steps To Reproduce:
1. Create a ContentAssistCommandAdapter in the createControl method of a Control
2. In the application open the corresponding view
3. Click into the field for which you created the ContentAssistCommandAdapter (in the sample below fSearchString)
4. The light bulb with tooltip "Content Assist Available (Ctrl+Space)" shows up, as expected
5. Close and reopen the application
6. The view is loaded automatically when the perspective is restored.
7. Click into the field with the ContentAssistCommandAdapter
6. The light bulb shows up with a tooltip saying "Content Assist Available (null)"--obviously the key binding has not been loaded correctly
7. Close and reopen the view and click into the field again
8. The tooltip says "Content Assist Available (Ctrl+Space)" now


More information:
Code snippet:

public void createControl(Composite group) {
  new ContentAssistCommandAdapter(
    fSearchString, 
    new ComboContentAdapter(), 
    fProposalProvider,
    ITextEditorActionDefinitionIds.CONTENT_ASSIST_PROPOSALS,
    null, true);
}
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:32:30 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.