Code: Select all
LBL "TEST"
MAN
PRON
0
STO "GrMod"
5
5
CLLCD
PIXEL
PRLCD
CLLCD
2
STO "GrMod"
100
100
CLLCD
PIXEL
END
Is this normal behaviour or a bug?
Code: Select all
LBL "TEST"
MAN
PRON
0
STO "GrMod"
5
5
CLLCD
PIXEL
PRLCD
CLLCD
2
STO "GrMod"
100
100
CLLCD
PIXEL
END
Code: Select all
>LBL "TEST"
0
XEQ 14
5
ENTER
CLLCD
PIXEL
STOP
CLLCD
2
XEQ 14
100
ENTER
CLLCD
PIXEL
RTN
>LBL 14
STO "GrMod"
END
Thanks for looking at this. I ran the code as you wrote it and had exactly the same behaviour whether I include the CLLCD just after the STOP or not. The CLLCD is not CLing the LCD. Same firmware as you.
If the program pointer points *at* the RTN, something is wrong; the CLLCD has caused program execution to stop. When a program encounters a RTN with an empty return stack, it behaves like STOP, and the program pointer ends up pointing to the first line *after* the RTN.whuyse wrote: ↑Tue Apr 03, 2018 9:36 amI altered the program to remove the printing commands, and added a STOP after the first PIXEL. Executing first shows the pixel at (5,5).
Upon pressing R/S, the busy annunciator remains lit, and the result of drawing the pixel at (100,100) is not shown. Pressing PRGM shows the code has run till the end (RTN before the LBL 14).