#9777: Improve breakpoint list editing -------------------------------------+---------------------------- Reporter: bonefish | Owner: anevilyak Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Applications/Debugger | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -------------------------------------+---------------------------- Comment (by anevilyak): Replying to [comment:2 bonefish]: > I don't know what additional detailed information you're thinking about displaying for watchpoints, but I guess the same can be done in a joined table. The column names might have to be generalized a bit. In the case of a breakpoint, the information of interest is the source location the breakpoint is at. For a watchpoint however, the pertinent information that I had in mind was the address, size and type (read/write) of watchpoint. Other than enabled/disabled state, there really isn't any overlap between the two, so to me it would seem a bit messy UI-wise to try and have both in the same table with redundant/unused columns just to be able to accomodate that. > * The table model classes lack editing capabilities. With those it would be a lot easier to implement table editing operations (at least removing and moving rows) in a general way. > * ... particularly with a helper proxy model that joins a list of other models. This way separate models could be implemented for breakpoints and watchpoints. That would indeed be nice/helpful in general, but given the above, I really don't think it makes handling this particular case any cleaner. It's also not just the models in general that are the issue on the code side, but also e.g. selection listener hooks and such. -- Ticket URL: <http://dev.haiku-os.org/ticket/9777#comment:3> Haiku <http://dev.haiku-os.org> Haiku - the operating system.