Quote:

I mean, if he placed the text on the screen with AT(), and was careful not to let it overflow and scroll, he would know where to put the checkmark AT().



My guess is that the screen output will comprise both text from the script, and output from commands that are run.

To know where he is he needs to capture the output (including errors) from the commands, work out the console size, displays the output using KiXtart and calculate the cursor position (taking into account screen scrolling).

He may well be handing control to a program which he cannot capture output from, so cannot determine where on the screen the cursor will be left.

It's pretty heavy stuff and guaranteed to fail in some cases.

FWIW I've always thought it would be useful to allow the AT() parameters to be optional, and/or have macros which return the cursor position. It's such a simple process I'm surprised it hasn't made it in despite repeated requests. Perhaps it just wasn't popular enough.