[haiku-bugs] Re: [Haiku] #9777: Improve breakpoint list editing

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Sun, 19 May 2013 23:41:02 -0000

#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 bonefish):

 Replying to [comment:3 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.

 I think, at least partially this can be remedied by generalizing the
 column names/meaning. The source file and line column (could be be joined
 BTW) would indeed not be applicable for watchpoints. The "Function"
 column, however, could be renamed to "Location" and could contain the
 relevant info for watchpoints (e.g. "read at 0xf00ba1 (4 bytes)").

 Note, that I certainly don't think this is the perfect or even best
 solution, but I'd really like to avoid a "Watchpoints" tab. We don't have
 many tabs yet, but there are plenty of team-wide entities/concepts that
 may get their own tab eventually (global variables, areas, signals,
 locking primitives,...), that having separate ones for break- and
 watchpoints seems excessive. Showing two list views in the breakpoints
 page (at the same time) is a no-go due to the very limited space, so there
 would have to be a means to switch between them -- a combo box or radio-
 style toolbar buttons.

--
Ticket URL: <http://dev.haiku-os.org/ticket/9777#comment:4>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: