This indeed looks like a bug to me, something to do with the interaction between PX and SETPIXEL. The bug is not reproducible in MSWLogo, so it's something that I introduced along the way.
Here's a simpler repro
px fd 1 setpixel 3
It looks like you need to move at least one pixel in PPT mode to put SETPIXEL into a working state.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your suggested fix looks correct to me. I plan to fix this after doing some other cleanup tasks from removing the Borland OWL code, but my fix will closely resemble your fix (although it will probably include a regression test).
When you say "I add" and "it works", does that mean you can compile and build FMSLogo?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This indeed looks like a bug to me, something to do with the interaction between PX and SETPIXEL. The bug is not reproducible in MSWLogo, so it's something that I introduced along the way.
Here's a simpler repro
It looks like you need to move at least one pixel in PPT mode to put SETPIXEL into a working state.
Your suggested fix looks correct to me. I plan to fix this after doing some other cleanup tasks from removing the Borland OWL code, but my fix will closely resemble your fix (although it will probably include a regression test).
When you say "I add" and "it works", does that mean you can compile and build FMSLogo?
I am now tracking this as a bug [#472] (instead of a discussion)
Related
Bugs:
#472