Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361207 - The variable hovering in the RichUI debug does not work
Summary: The variable hovering in the RichUI debug does not work
Status: CLOSED DUPLICATE of bug 351872
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 03:00 EDT by fahua jin CLA
Modified: 2017-02-23 14:18 EST (History)
3 users (show)

See Also:

Attachments
The sample project. (19.86 KB, multipart/x-zip)
2011-10-18 03:48 EDT, fahua jin CLA 		no flags Details
View All 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 fahua jin CLA 2011-10-18 03:00:43 EDT 
Build Identifier: 0.7.0.v201110172101

1) Create a new workspace, and import the attached project to the workspace.
2) Open H2.egl in the client package.
3) Set a break point in line 30.
4) Right click the H2, and debug it.
5) The break point is hit, while if I move the mouse to the retResult variable, the value of the variable cannot be displayed.

Reproducible: Always
Comment 1 fahua jin CLA 2011-10-18 03:03:38 EDT 
I think the variable hovering function should be supported in the EDT, and set the defect priority to major. Let's discuss if you do not agree with it. Thanks.
Comment 2 fahua jin CLA 2011-10-18 03:48:54 EDT 
Created attachment 205391 [details]
The sample project.
Comment 3 Justin Spadea CLA 2011-10-18 09:45:36 EDT 
We do not currently support hover value. It is a feature that will be added to 1.0. This is not an oversight but we decided during planning to defer it. See bug 351872.

*** This bug has been marked as a duplicate of bug 351872 ***
Comment 4 fahua jin CLA 2011-10-18 20:12:03 EDT 
I close the defect... I did not check against the opened enhancement before opening the defect.