![]() | |
#11
| |||
| |||
|
|
The only problem is that the D3 debugger shows the line you have *just* executed, and by that time, you are already into the subroutine. It would be more useful if the D3 debugger (which I hate) would show you the line you were *about* to execute. |
#12
| |||
| |||
|
|
Bob Little wrote: The only problem is that the D3 debugger shows the line you have *just* executed, and by that time, you are already into the subroutine. It would be more useful if the D3 debugger (which I hate) would show you the line you were *about* to execute. One-stepping through debug isn't done in a vacuum. That is, your knowledge of the program isn't completely limited to the one line you happen to be looking at. If you're on line 105, use a command like L90-115 to see the lines above and below where you are. You will easily see all of the lines about to be executed after 105. Yes, I know. Extra steps though. My point is that if the Ultimate |
|
Lighten up guys. These tools aren't perfect but we've been workingwith them for 20-odd years and they probably aren't going to change much - get use to them already. I *was* used to it, I guess that's the problem. I tend to resist change |

#13
| |||
| |||
|
|
Small world, I'm in Wilmington, NC. :P Glen |

#14
| |||
| |||
|
|
My point is that if the Ultimate Basic debugger (both during the Ultimate OS period and the UltPlus days) did what I mentioned back in the 80s, why can't D3 do it now? |
|
I *was* used to it, I guess that's the problem. I tend to resist change sometimes - even if it's a change for the worse. Go figure. ![]() |


#15
| |||
| |||
|
|
Yes, I know. Extra steps though. My point is that if the Ultimate Basic debugger (both during the Ultimate OS period and the UltPlus days) did what I mentioned back in the 80s, why can't D3 do it now? |
![]() |
| Thread Tools | |
| Display Modes | |
| |