Debug - goto and line number
Posted: Sun Mar 21, 2010 2:29 pm
Currently, the Debug statement outputs a text string to the debug window, with a preceding timestamp.
I would like to add two options, to speed up debugging:
1. A line number, like this:
Yeah, I can do it with a macro like this, I know, but I'd like to have it as a an option in the debugger...
2. A doubleclik / goto action...
When doubleclicking (or control doubleclicking) on a line in the debug output window, I'd like the editor to jump to that line. In other words, if I'd doubleclick on the line [14:26:21 1223] above, the editor should jump to line 1223.
I think these two additons could seriously speed up debugging, for example when you're spreading around 'Debug' statements to figure out what is going on, you a. know where the debug is located whose output you're looking at, and b. you can more easily get rid of 'forgotten' debugs, and c. you can leave Debug statements in for other parts of your code, without having to skip them every time you search for other Debug statements that you want to get rid of.
Code: Select all
[14:26:21] whatever
1. A line number, like this:
Code: Select all
[14:26:21 1223] whatever
Code: Select all
Macro x_debug(text)
Debug "line "+Str(#PB_Compiler_Line)+" - "+text
EndMacro
When doubleclicking (or control doubleclicking) on a line in the debug output window, I'd like the editor to jump to that line. In other words, if I'd doubleclick on the line [14:26:21 1223] above, the editor should jump to line 1223.
I think these two additons could seriously speed up debugging, for example when you're spreading around 'Debug' statements to figure out what is going on, you a. know where the debug is located whose output you're looking at, and b. you can more easily get rid of 'forgotten' debugs, and c. you can leave Debug statements in for other parts of your code, without having to skip them every time you search for other Debug statements that you want to get rid of.
<very innocent look>