Forum
Nice, reminds me of my youth. :)
When I'm editing in the list window, the cursor jumps to the end of the list immediately after each keystroke.
Then I have to painstakingly search for where I was. You can put an asterisk (*) before the line number, but that's just as cumbersome. Am I doing something wrong, or is this how it's supposed to work?
How do I use the debug window?
The "Renumber" tool doesn't recognize "DO" and "DO BLOCK".
I haven't found anything about this in the documentation.
But it's fun!
When I'm editing in the list window, the cursor jumps to the end of the list immediately after each keystroke.
Then I have to painstakingly search for where I was. You can put an asterisk (*) before the line number, but that's just as cumbersome. Am I doing something wrong, or is this how it's supposed to work?
How do I use the debug window?
The "Renumber" tool doesn't recognize "DO" and "DO BLOCK".
I haven't found anything about this in the documentation.
But it's fun!
Replies
2026-02-24 08:44:07 —
@Basic32
@Basic32
👍 0 • 👎 0
If you want something to show up in the Debug Panel of Basic32 Terminal, a normal PRINT is not enough.
You must include the #DBG prefix in the text.
Example:
10 A = AREAD(36)
20 PRINT "#DBG ADC="; A
30 WAIT 200
40 GOTO 10
Then run the program with RUN, and in the Debug Panel you’ll see:
Copia codice
ADC=1234
ADC=1240
...
The #DBG part is not displayed — it’s just used by the terminal to recognize debug lines
You can replace #DBG with whatever you want.
You must include the #DBG prefix in the text.
Example:
10 A = AREAD(36)
20 PRINT "#DBG ADC="; A
30 WAIT 200
40 GOTO 10
Then run the program with RUN, and in the Debug Panel you’ll see:
Copia codice
ADC=1234
ADC=1240
...
The #DBG part is not displayed — it’s just used by the terminal to recognize debug lines
You can replace #DBG with whatever you want.
Write a reply
You must log in to reply.