Bug 215887 - [Markers] Marker table in MarkerResolutionDialog needs more details
Summary: [Markers] Marker table in MarkerResolutionDialog needs more details
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-19 11:41 EST by Grace Wong CLA
Modified: 2019-09-06 15:37 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 Grace Wong CLA 2008-01-19 11:41:43 EST 
I extended WorkbenchMarkerResolution to provide quick fix for a problem and allosed similar problems in the same file to be fixed at the same time.

Here's what shows up in the table (1st column is file name, 2nd column is line number), which doesn't tell much

Problems: 
   <filename>.<extension> and Unkn... 
   <filename>.<extension> and Unkn... 
   <filename>.<extension> and Unkn... 

Line number is not always relevant (for example, I have a GEF editor for editing a EMF model).  It will be nice if I can configure:
1) How many columns to show
2) Which marker attribute to show in which column
Comment 1 Tod Creasey CLA 2008-01-21 12:44:26 EST 
We could make this match the view that created it potentially
Comment 2 Grace Wong CLA 2008-01-21 14:12:07 EST 
This sounds good.
Would it be possible to make the columns resizable?
Comment 3 Tod Creasey CLA 2008-01-21 14:28:51 EST 
Yes it would
Comment 4 Tod Creasey CLA 2008-01-21 14:29:54 EST 
BTW Grace this has already been improved significantly in 3.4. You should take a look there and then give me more feedback if possible.
Comment 5 Susan McCourt CLA 2009-07-15 12:18:02 EDT 
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:37:12 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.