BreakpointWidget: Add ability to directly edit breakpoints

[TryTwo]

Add theme-aware buttons, ability to edit addresses, and a popup for conditional editing.

If a base address is changed, it will delete the breakpoint and then create a new breakpoint at the new address. Useful for moving a conditional to another address.

Removed selecting rows, which breaks the old delete button. Delete moved to context menu.

This new style can result in new odd states for breakpoints. Such as a Memory Breakpoint that is enabled, but has Read + Write disabled, resulting in nothing being done. Previously Read and/or Write would always be true. Not sure it matters.

If the buttons are no good, they can be replaced with 3-state combo boxes. Break/Log/B+L.

[dreamsyntax]

I'm really liking it so far.

The only thing I'm iffy on is in the case of the memory breakpoints, as you called out in your initial post.

Would it be possible to give a 'disabled' tint state to a row that wont ever result in a hit?

[TryTwo]

I added it. Note that changing Dark/Light style doesn't send a signal to update, so you have to manually cause the widget to update if you want to test both styles.

[dreamsyntax]

I added it. Note that changing Dark/Light style doesn't send a signal to update, so you have to manually cause the widget to update if you want to test both styles.

This is actually not what I meant. But this is a good change in any case.
I meant the entire row of a BP state that will never result in a hit.

Per my screenshot above, I would expect row2 to be entirely grayed out as the 'active' is not checked.
Similarly if active is checked, but no read/write is checked, it should also be grayed out.

The idea was to indicate if a current BP is 'inactive' by implicit state - as this sort of solves the case of weird BP configurations and not realizing it.

[TryTwo]

Oh, my bad. That's a nice idea to deal with weird states in the UI, if the text is still readable. I wonder if I can do it without setting the color for each cell.

[dreamsyntax]

Yeah, im not sure if its feasible. Was just an idea.

That aside, ive been using this build for a while now, its really a great improvement as is.

[dreamsyntax]

Tested latest commit (dbacb60) a bunch in real world usage.

LGTM. While it would be nice to handle what we discussed above, it's not really detrimental to usage as is.
Maybe in a future PR.

I think this is worth merging as is.

[TryTwo]

[dreamsyntax]

<image of row disabling/colors>

Did you not push your latest change? It doesn't seem to be working like that for me.

[dreamsyntax]

I've been using this for about 2 weeks, with the latest (disable state UI state adjustment) for about a week. It's overall a much better debugging UX.

Thoroughly tested the disable color states for MBP. Everything looks good to me. I think this should be merged.

[TryTwo]

@sepalani Are you interested in reviewing?

[AdmiralCurtiss]

Squashed the fixup commits. I haven't tested this but if you say it works fine I'll believe you, it seems like a massive usability improvement.