on your next update of the kernel - would it be possible to send out a "?" just before the DEBUGIN accepts input?
other terminal programs don't give any indication of an input request (ie. TclTerm.tcl)
This is similar to the old-style INPUT command.
I stick it (DEBGIN)in my program and forget about it - thinking the program has hung---
this CAN ALSO occur if the cursor happens to be in the data output (terminal) window instead of the "Enter window"
// sloppy window usage - with several windows open on the desktop - I just click in the terminal window to select it
// so I can do a 'reload file'
originally I included RXD in my suggestion - but upon further thought - if you are doing a bunch of serial data exchanges
you may not want the '?' being transmitted, whereas DEBUGIN is expected to be a one-way transfer of info
Thanx from an OL' timer
debugin modification
Re: debugin modification
I would strongly disagree with adding it before RXD(0), as that is often the way BASIC communicates with the PC.
If you want to send something to the PC to tell -- Heh send me something, that is up to you.
Now the case for DEBUGIN is a little different and I could see your argument, but while it could be done in the compiler, probably better handled in firmware. It could also be done by --
While DEBUGIN handles STRING or INTEGER it does not handle SINGLE, and frankly with next to no room left in the M0 firmware it won't, but you could write that routine yourself.
If you want to send something to the PC to tell -- Heh send me something, that is up to you.
Now the case for DEBUGIN is a little different and I could see your argument, but while it could be done in the compiler, probably better handled in firmware. It could also be done by --
Code: Select all
function ZEKE_INPUT()
DIM I
PRINT "?";
DEBUGIN I
return I
END FUNCTION
While DEBUGIN handles STRING or INTEGER it does not handle SINGLE, and frankly with next to no room left in the M0 firmware it won't, but you could write that routine yourself.