Breakpoint icons in the Breakpoint Navigator coloring/dimming is extremely confusing

Originator:nimayousefi1
Number:rdar://18529835 Date Originated:02-Oct-2014 12:56 PM
Status:Open Resolved:
Product:Developer Tools Product Version:Version 6.1 (6A1042b)
Classification:Serious Bug Reproducible:Always
 
Summary:
I use a lot of breakpoints, and in Xcode 6.1 the way breakpoints are colored/dimmed in the Breakpoint Navigator is extremely confusing. I've attached 4 screenshots to illustrate this--

1.png: opArray() line 350 is selected in the navigator. This breakpoint is *active*, but is dimmed to almost the same color as opStringWithNewline() below it, which is *inactive*.

2.png: Selection is changed to opStringWithNewline(), showing that opArray() was active.

3.png: The opStringWithNewline() breakpoint has now been *activated* by clicking on the breakpoint icon in the navigator. Note the very subtle change in color.

4.png: The breakpoint for opStringWithNewline() was inactivated by clicking on the breakpoint icon directly in the editor (also shown). Note that the icon in the editor is correctly dimmed, but the icon in the Breakpoint Navigator is now darker than the inactivated breakpoints around it, because the Breakpoint Navigator no longer has focus.

It is extremely difficult to tell what is and isn't active, and under certain cases, like the ones in 1.png and 4.png, the state of the breakpoint is counter intuitive.

Steps to Reproduce:
1. Open an Xcode project.
2. Add breakpoints.
3. Turn some off and some on.

Expected Results:
The difference between active and inactive breakpoints should be extremely clear and obvious.

Actual Results:
It is not.

Version:
Version 6.1 (6A1042b)

Notes:


Configuration:


Attachments:
'1.png', '2.png', '3.png' and '4.png' were successfully uploaded.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!