If Code has the following form:
followed by _DISPLAY, the images are placed on the screen in the order Image1&, Image2&, Image3&, and Image2& is on top of Image1& and occludes it (as you would expect), and Image3& is on top of Image2& and occludes it and Image1& (as you would expect).
I found a curiosity with _MAPTRIANGLE3D, where the opposite happens:
_MAPTRIANGLE(a
,b
)-(c
,d
)-(e
,f
), Image1&
TO(x1
,y1
,z
)-(x2
,y2
,z
)-(x3
,y3
,z
) _MAPTRIANGLE(a
,b
)-(c
,d
)-(e
,f
), Image2&
TO(x1
,y1
,z
)-(x2
,y2
,z
)-(x3
,y3
,z
) _MAPTRIANGLE(a
,b
)-(c
,d
)-(e
,f
), Image3&
TO(x1
,y1
,z
)-(x2
,y2
,z
)-(x3
,y3
,z
)
followed by _DISPLAY puts Image2& on top of Image3&, and Image1& on top of Image2& and Image3&.
Note that all images have the same z value and are all in the same z- plane. If z- values differ, then the images will be placed in z- value order (lowest z-, ie furthest away, first).
This opposite ordering is a curiosity, and I've learnt to change the code order for _MAPTRIANGLE3D.
Do the parameters _CLOCKWISE /_ANTICLOCKWISE have any effect upon this? I have never used _CLOCKWISE /_ANTICLOCKWISE, as I cannot fathom what is the "thing" that is going anticlockwise or clockwise. You are just writing images to the screen in a particular order.