It took me a while -- as in, time spent inspecting code and debugging app -- to realize that cls(a) ignores prior pal(a,b) calls, hence filling the screen with a.

Assuming this is not a bug, it would be good to mention this in the docs for that function.

Cheers.

PAL only affects CLS if you include the last param as 1 (display palette):

PAL(0,15)
CLS(0) -- clears as black

while

PAL(0,15,1)
CLS(0) -- clears as tan

My guess is the CLS is not coded as a "draw" operation and so uses the display palette instead of the draw palette.

Thanks! Just what I needed (that, and a second reading of pal's docs :p ).

also cls clears the draw state, so it makes sense than a palette swap is reset before the screen is filled