Bug 84545 - [content assist] Parameter Hint Popup left over
Summary: [content assist] Parameter Hint Popup left over
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 262597 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-07 04:26 EST by Kai-Uwe Maetzel CLA
Modified: 2019-09-06 15:30 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai-Uwe Maetzel CLA 2005-02-07 04:26:24 EST
I20050201-0800

1) Enter the following text

import org.eclipse.swt.layout.GridLayout;
import org.eclipse.swt.widgets.Composite;
import org.eclipse.swt.widgets.Label;

public class TextEntryField extends Composite {

	public TextEntryField(Composite parent, int style) {
		super(parent, style);
		
		GridLayout layout= new GridLayout();
		layout.numColumns= 6;
		layout.makeColumnsEqualWidth= false;
		
		Label label= new Label(this);
	}
}

2) Place caret at Label(this>I<);
3) Ctrl+Shift+Space
4) Type ",SWT"
5) Invoke content assist to get the import
-> Import statement is inserted, Parameter Hint Popup is off by one line
6) move caret to end of line
7) Press enter
8) type "label.setVisib"
9) invoke content assist
-> method completion etsablishs a new Parameter Hint Popup
-> When the caret leaves the method call, the popup established in 3 reappears
Comment 1 Dani Megert CLA 2005-02-07 06:12:58 EST
Might be caused by fixing bug 67327. Works in 3.0 (but param hint goes away as
soon as line is shifted due to added import).

Kai, can you please add the steps you mentioned which do not include the import
being added - thanks.
Comment 2 Dani Megert CLA 2009-01-28 06:29:10 EST
*** Bug 262597 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:30:44 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.