Community
Participate
Working Groups
Whenever one sets up enough of the powerfull exception breakpoints, they become annoyingly omnipresent. The user normally wants to add/remove/enable/disable the source breakpoints, but much less frequently the exception breakpoints as they are kind of a protection while developping, to trap a problem on the fly when not expected (especially usefull with the exclude/include location). Since they are not acessed often, they should be grouped under a treenode, collapsed or not to the user choice. The extra mile: Hovering the breakpoint should document its included/excluded locations. Also, you could create other subnodes like caught/uncaught, simply because the icon is totally useless since too small and the caught/uncaught text is pollution and requires the simple breakpoint view to be larger fo no reason, reducing space for other views. From there, you can imagine drag'n'dropping exception location from caught to uncaught, or from included to excluded, or from package to class and so on... whatever.
Instead of a hard-coded auto-grouping feature, I'd prefer to provide either generic support to create your own breakpoint groups (which would be rendered using a tree) and/or make it possible to reorder breakpoints in the view.
Awesome. As long as it is clear to which project they belong, because I have filed a bug about duplicate breakpoint at #67705
*** This bug has been marked as a duplicate of 44986 ***
