Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 70380

Summary:	Current statement arrow obscures breakpoint icon
Product:	[Eclipse Project] Platform	Reporter:	Walter Gillett <walter_gillett>
Component:	Debug	Assignee:	Platform-Debug-Inbox <platform-debug-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	minor
Priority:	P3	CC:	manthrax, sarika.sinha
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Walter Gillett

2004-07-19 16:58:19 EDT

When I started using Eclipse 3.0 (which I love, BTW!) I was confused by 
trouble clearing breakpoints.  When I hit "Toggle Breakpoint" the breakpoint 
didn't seem to go away.  Finally figured out that the current statement arrow 
was sitting in front of the breakpoint icon, obscuring the change in status, 
and it wasn't obvious that there was an arrow at that position rather than a 
breakpoint.  Not sure what this looked like with Eclipse 2.x but I don't 
recall having this problem.  Suggest using a more distinctive color/shape for 
the arrow to make it visually easier to distinguish from the breakpoint.

Minor issue but seemed worth reporting.

Comment 1 Jared Burns

2004-07-26 13:33:09 EDT

It would be nice if we had a better way to display multiple markers on the same line. Maybe we'd want 
one icon that means "multiple markers here." Highlighting it would show the hover text for all the 
markers and clicking on it would display them in some kind of pop-up? Not sure that that's the best way 
to do it, but I think it'd be an improvement on what we have today.

Comment 2 Darin Wright

2004-07-26 13:44:02 EDT

This is really an issue for the editor framework. A similar problem exists if 
there is a quick fix and breakpoint on the same line. A double click in the 
ruler will invoke the quick fix rather than get rid of the breakpoint. 
Displaying/distinguishing editor ruler annotations should be the job of the 
editor, not the debugger.

Comment 3 Dani Megert

2004-07-26 13:47:11 EDT

No it is not. The double-click problem is on our side and there's a bug for it.
However, if you specify in your plugin.xml that the arrow is above the
breakpoint then well, we do what you ask us for i.e. arrow will hide breakpoint.
The annotation-rollover story is a first step to solve this issue.

Comment 4 David Williams

2004-07-26 20:08:36 EDT

Just thought I'd add that this is indeed a continuing minor frustration for me 
too (that is, its not something that easy to "get used to"). I think the reason 
this is a such as frustration is that the breakpoint on the current line is one 
that you frequently want to interact with, clear, disable, set properties, etc. 
And, sometimes, I even have to look up at the stack trace to figure out why it 
stopped on that line ... was it a breakpoint, or an uncaught exception?

Comment 5 Darin Wright

2004-07-29 15:55:17 EDT


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

Comment 6 Michael Schlachter

2014-02-24 18:04:14 EST

This was reported TEN YEARS AGO, and is STILL an issue in all versions of eclipse and Android Dev Kit.

This is IMO, INEXCUSABLE, and is the reason that Eclipse is going to be replaced by superior editors such as JetBrains.

Good Job, and GOOD RIDDANCE.

Comment 7 Sarika Sinha

2014-02-28 06:09:00 EST

See the 

General > Editors > Text Editors > Annotations pref page for setting breakpoint annotations

you can now set a variety of annotations for breakpoints that will hi-light, underline, etc the breakpoint in the editor.