| Summary: | Editing breakpoint collection before a debugging session | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Markus Elfring <Markus.Elfring> |
| Component: | CPP Debugger | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | niko.sams |
| Priority: | NOR | ||
| Version First Reported In: | 5.2.4 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Markus Elfring
2018-10-07 14:40:40 UTC
This is already possible. Two ways to do it: 1) Right-click on a toolbar in the main window (left, right or bottom): [x] Breakpoints 2) Go to Window -> Tool Views -> [x] Breakpoints (In reply to Kevin Funk from comment #1) Now I have noticed that I had to enable the tool view “Breakpoints” explicitly. * Can another menu entry make sense below “Execute -> Switch breakpoint on/off”? * How should the condition be modified there? > Can another menu entry make sense below “Execute -> Switch breakpoint on/off”? I don't think so. It doesn't really make sense to have an action to trigger tool views on/off there. > How should the co=ndition be modified there? Hm? Please explain. (In reply to Kevin Funk from comment #3) I would find an additional menu entry like “Execute -> Edit breakpoint list” helpful. Will the conditions vary between supported breakpoint types? > Will the conditions vary between supported breakpoint types?
Still no idea what you mean. Maybe you're better off asking on the mailing list? This bug report is already convoluted and no longer is about one single task/issue.
(In reply to Kevin Funk from comment #5) It seems that we have got different user interface expectation for the activation of breakpoint listing. > Still no idea what you mean. Which conditions are supported for the four breakpoint types so far? |