Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318029 - Content assist in Variables view uses wrong context
Summary: Content assist in Variables view uses wrong context
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 4.13 M3   Edit
Assignee: Sarika Sinha CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-25 14:20 EDT by Markus Keller CLA
Modified: 2019-08-05 02:52 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 Markus Keller CLA 2010-06-25 14:20:18 EDT
N20100620-2000

Content assist in the Variables view uses a wrong context.

I had a breakpoint on the last line of org.eclipse.jface.text.AbstractInformationControlManager.computeAvailableArea(Rectangle, Rectangle, Anchor). I selected the local variable 'area' of type 'Rectangle' in the Variables view. In the details pane, I wanted to write
"Geometry.copy(bounds)" and save that into 'area'. The expression is perfectly valid and it worked, but content assist didn't have any proposals after "Geo" nor after "Geometry.co".

Looks like you use the context of the selected variable's type (SWT), but you should use the context of the selected stack frame's type (org.eclipse.jface.text, which depends on JFace, which defines the class Geometry). Or maybe both contexts, I don't know what exactly the expression evaluation engine supports.
Comment 1 Eclipse Genie CLA 2019-08-04 16:23: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.

--
The automated Eclipse Genie.
Comment 2 Sarika Sinha CLA 2019-08-05 02:52:53 EDT
Works well with
Eclipse SDK

Version: 2019-09 (4.13)
Build id: I20190731-1800