Bug 396227 - [breakpoints] Breakpoint properties Common page contributions should show a hierarchy
Summary: [breakpoints] Breakpoint properties Common page contributions should show a h...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 8.1.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords: polish
Depends on:
Blocks:
 
Reported: 2012-12-10 17:52 EST by Pawel Piech CLA
Modified: 2020-09-04 15:16 EDT (History)
3 users (show)

See Also:

Attachments
Screenshot. (31.33 KB, image/png)
2012-12-10 17:52 EST, Pawel Piech CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Piech CLA 2012-12-10 17:52:05 EST 
Created attachment 224538 [details]
Screenshot.

This is a polish item for the breakpoint properties dialog.

The UI contributions which are added to the common page of the dialog allow for a hierarchy in the contributions.  The hierarchy is such that lower-level contributions are added only if the higher level contribution's value matches a specified condition.

In CDT, the hierarchy of UI contributions is only exercised for event breakpoints.  When creating an event breakpoint, a hard-coded set of field editors is created with the lower-level field editor being indented.  After the breakpoint is created, the lower-level field editor is not indented anymore which is inconsistent.  This patch would fix that inconsistency and would also apply to any other UI contributions which use a hierarchy.
Comment 1 Pawel Piech CLA 2012-12-10 17:55:22 EST 
Posted proposed patch to gerrit: https://git.eclipse.org/r/#/c/9153/
Comment 2 Jonah Graham CLA 2019-12-30 17:05:10 EST 
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.