Debugging with _SCREEN.Print

[Toman]

For debugging I occasionally use commands like

_SCREEN.Print(cMyVar + CHR(13))

I think it has some advantages over WAIT WINDOW, MESSAGEBOX.
Unpleasant is, that this way I can use only some area of the screen to show results. I have a suspicion, that this part has the same height as the form, from where the command was issued.
If I run following code from Command Window

_SCREEN.Cls
FOR n = 1 TO 100
_SCREEN.Print(STR(n) + CHR(13))
ENDFOR

everything is all right – on my screen I can see at this moment rows from #1 to #60.
When run from a form, I can see only rows from #1 to let's say #20, with higher form more.
If I add coordinates to the command, the whole screen is accessible, but it is not convenient here.

Why the system behaves like that and can such behavior be override some way.
Thank you, Tom.

 

[TamarGranor]

I suggest you use DEBUGOUT instead and avoid the whole issue.

Tamar

 

[Toman]

Ooh shure, DEBUGOUT, this is the right way.
And much more better then SCREEN.Print. I need not to send LineFeeds, take care about variable type and output list can be endless and can be copied or saved easily.
Thank you Tamar very much.
Tom