At 15:11 2003-1-22 -0700, you wrote:
The line where the breakpoint has been hit will be shown in the debugger window, the one with the three panes, showing stack crawl, variables, and source view. However, you won't see it in the main source editor -- the debugger is really optimized for the all-in-one window.If I set a break point in file A.cpp and I launch the debugger while in file B.cpp, the code breaks, but focus does not go to the line where the break point is. Instead, I have to search for the break point that was hit by the code. This only happens when I do not have the files maximized in the IDE.
Ah... if you're in the all-in-one window, you can click on a previous stack frame, then click back on the current stack frame to be taken to the location of the next line to be executed.The visual studio command Show Next Statement is used to go back to current line of code you are on (while stepping through the code). This is a nice feature if you are tracing back through your function calls. You just select Show next statement, and the debugger brings to the next line of code that will be executed.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
