Bug 74217 - Add code assist to the Add Watch Expression dialog
Summary: Add code assist to the Add Watch Expression dialog
Status: RESOLVED DUPLICATE of bug 57580
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 99505 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-09-17 16:24 EDT by Ed Burnette CLA
Modified: 2005-07-07 13:52 EDT (History)
2 users (show)

See Also:

Attachments
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 Ed Burnette CLA 2004-09-17 16:24:39 EDT 
Debug a Java program, stop at a breakpoint, go to the Expressions window, 
right click, select Add Watch Expression. It would be nice to have code assist 
in this window. Same goes for the Edit Watch expression dialog.
Comment 1 Darin Wright CLA 2004-09-21 09:28:35 EDT 
Currently, the add/edit watch expression dialogs are generic to the debug
platform, and are used for all debuggers. Thus, no code assist. Marking as
later. We would need to infer a debug context, and provide extension points for
debuggers plug-in content assist function.
Comment 2 Ed Burnette CLA 2004-09-21 09:58:00 EDT 
I have a process question: why did you mark it as Resolved Later instead of 
leaving it as New (enhancement)? Later means post 3.1 (right?) but 3.1 plans 
are still being added to so it seems premature. Also the next person to 
request this won't find the existing request as easily because the query page 
filters out Resolved by default. Just wondering.
Comment 3 Darin Wright CLA 2004-09-21 10:02:42 EDT 
Marking as later doesn't neccessarily mean post 3.1. It means "not right now". 
Bugs can move from later to 3.1 as we go thru the 3.1 milestones. In debug, we 
try to keep the "in box" (new, re-opened, etc), small so we know what's been 
dealt with/considered.
Comment 4 Ed Burnette CLA 2004-09-21 10:58:35 EDT 
Ok, then maybe this page should be changed: 
http://bugs.eclipse.org/bugs/bug_status.html
"LATER: The problem described is a bug which will not be fixed in this version 
of the product."

I'm not trying to give you a hard time specifically (well, maybe I am :) but 
rather I'm just trying to better understand how the bug system is intended to 
be used. Cc'ing Jim to see if he has any insight.
Comment 5 Jim des Rivieres CLA 2004-09-21 11:09:45 EDT 
Darin,  Perhaps REMIND, rather than LATER, more accurately describes the state 
of affairs: "REMIND: The problem described is a bug which will probably not be 
fixed in this version of the product, but might still be."
Comment 6 Darin Wright CLA 2005-06-13 09:09:57 EDT 
*** Bug 99505 has been marked as a duplicate of this bug. ***
Comment 7 Darin Wright CLA 2005-07-07 13:52:06 EDT 
re-open  to mark as dup.
Comment 8 Darin Wright CLA 2005-07-07 13:52:18 EDT 

*** This bug has been marked as a duplicate of 57580 ***