I needed to do a sanity check to understand why the CIRCLE statement is so slow compared to a custom subroutine (creating circles with triangles) to create circles filled in with color.
The interpreter I’m using does not allow variables in the screen statement, and I couldn’t be bothered setting up that ability.
To the rescue: TiddlyWiki scripting to generate the code at runtime.
screen _newimage(200,200,<<thisScreen>>)
locate 1,1 : print "screen mode: " + <<thisScreen>>
circle (100,100), 75
_delay 2
</$list>