Code: Select all
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
PRINT ""
PRINT "SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
Code: Select all
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
PRINT ""
PRINT "SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
Code: Select all
BITMAP ENABLE
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
PRINT ""
PRINT "SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
Maybe I didn't understand correctly the issue, but I think it's the expected behavior. The PRINT command without the semicolon will make the cursor move to the next line ("line feed") and to the first column ("carriage return"). This is the BASIC language standard.To obtain the result you expect, instead, you have two alternatives. The first is to print a string that contains a command to move the cursor. For example:
Code: Select all
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
PRINT CDOWN$;
PRINT "SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
Code: Select all
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
CDOWN
PRINT "SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
Code: Select all
downALine = CDOWN$
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
PRINT downALine;"SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
I tried it but it works fine:
Code: Select all
BITMAP ENABLE
downALine = CDOWN$
CLS
FOR i= 1 TO 20
PRINT "SOME TEXT";
NEXT
PRINT downALine;"SHOULD BE AT BOTTOM"
WAIT KEY RELEASE
Have you tried downloading the latest COLDFIX I posted today, and forcing a recompilation before running the program?
Yes, I am. I have used both version 1.2 and version 1.8.
It could be. Just today, with another developer, we discovered that XRoar does not behave the same if you load a binary image (BIN) and a disk image (DSK). If in doubt, try compiling a disk image and running the RUN"LOADER command.