Breakpoints appear as verified if verified by at least one session

[roblourens]

I don't know whether this was suggested before. Now we show red breakpoints only when the bp is bound in the selected debug process, and gray otherwise. I think it would be really helpful to be able to tell the difference between a breakpoint that isn't bound anywhere, and one that is bound but in a different process from the selected one. Often I want to check that my breakpoints are bound, and have to check the list of debug processes to make sure.

So we would see something like

• Red: bound in selected process
• Dark red: bound in some process, not the selected
• Gray: not bound anywhere

cc @weinand

[weinand]

This proposal makes a lot of sense.
We just have to keep in mind that for accessibility reasons the shape should differentiate the breakpoint state as well.

[isidorn]

Dark red feels stronger than red. Shouldn't that decoration be less strong since it is not currently bound?
PR welcome

Code pointer
https://github.com/Microsoft/vscode/blob/469786a7913ef99199d54683e0187c7e8e7e6f89/src/vs/workbench/parts/debug/browser/breakpointsView.ts#L569

[roblourens]

By "dark red", I'm imagining something like a cross between gray and red. The "bright red" we have should look stronger and "active". I have no idea how the shape should be differentiated.

[vscodebot]

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[roblourens]

This one really bugs me every day, can we keep it?