| Title: | Digital Ladebug debugger |
| Moderator: | TLE::LUCIA |
| Created: | Fri Feb 28 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 969 |
| Total number of notes: | 3959 |
As of 4.0-29: Pressing the scope stack button in dxladebug always starts out by pointing at scope level 0. It would be much more convenient to start the pointer in the current scope. - Matt
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 807.1 | TLE::MURRAY | Wanfang Murray | Mon Feb 24 1997 07:31 | 9 | |
When you click on the callstack button right now, it shows
a list of scopes starting from scope 0 no matter where
you are in the scope. Are you suggesting to have the current
scope line up with the callstack label to give you a hint
where you are now at the stack?
Wanfang
| |||||
| 807.2 | DECCXL::OUELLETTE | Mon Feb 24 1997 13:48 | 1 | ||
I think that's what Matt expected. It'd be what I'd like to see. | |||||
| 807.3 | DECC::MJHANS | Matthew Hanselman, DEC C | Mon Feb 24 1997 14:13 | 20 | |
Currently, clicking on the scope stack button will start you at level
0, even if you are actually in level (for example) level 10.
Since jumping around scopes is usually fairly local (e.g. moving from
scope level 10 to scope level 11), it makes more sense to start the
mouse at level 10 rather than level 0. When I want to go down one
level I'd like to just hit the scope button and move the pointer down one
level -- not hit the scope button, start out at 0, figure out where I
was, and go searching from there.
Like the joke:
Joe took a job painting the lane markers on streets. The first day he
did really well: 10 miles. The next day, not quite as well: only 6
miles. Then 4 miles the next day, etc. His productivity continuously
went down, until his boss approached him and asked him why. Joe's
answer was simple: "Well, each day, I keep getting further away from
the can of paint....."
- Matt
| |||||