Community
Participate
Working Groups
The following enhancement would allow multiple breakpoints, which form a logical group or debugging task, to be enabled/disabled together. Rules: - Each breakpoint may belong to zero or more groups - Each group can be either enabled or disabled - Breakpoints can be manually enabled or disabled, apart from any group status - User should be able to clear the manual override (whether enable or disable) - A breakpoint is enabled if: * any of the groups it belongs to is enabled, unless it has been disabled manually * or, it has been enabled manually - When disabling a group, if any member breakpoints have been manually enabled, they will remain enabled after the group has been disabled - When enabling a group, if any member breakpoints have been manually disabled, they will remain disabled after the group has been enabled - When initially creating a group from a set of existing breakpoints, the group will be enabled if any of the members are currently enabled. Any other disable members will be marked as "manually disabled" - Breakpoints can be added/removed to groups at any time. Doing so should not affect their effective enabled status (ie. use manual overrides as necessary) - Breakpoints not belonging to any groups will behave as they do today I envision each breakpoint really having two internal flags - a tristate flag (null, true, false) indicating the manual override; the other being the calculated from its group memberships. The effective enabledness is determined based on a combination of these, according to the rules above. There are probably issues or grey areas I haven't foreseen. Discuss away!
Breakpoint groups do exist. You can create breakpoint working sets, and display by groups in the view. Or you can group by resource, project, type, etc.. Use the "Group By >" submenu on the view drop-down menu (the little triangle at the top right corner of the view). *** This bug has been marked as a duplicate of bug 80136 ***
