Line A Routines
*** And wait for mouse button release
wait:
move.w M0USE_BT(a5),d3
btst #l,d3
bne wait
*** end program
move.l #0,-(sp) * GEMDOS terminate command
trap #1 * call GEMDOS and exit
*** Data for input is stored here
.data
*** mouse pointer data
dc. w 8,8,1,
0,2
dc.w $OFFO, $0FF0, $0FF0,
$FFFE
dc.w $FFFE, $FFFE, $FEFE,
$FC7E
dc.w $FEFE, $FFFE, $FFFE,
$FFFE
dc.w $OFFO,
$0FF0, $0FF0,
$0000
dc.w $0 0 0 0, $0 0 0 0,
$0380, $0380
dc.w $0380, $3FF8, $3EF8, $3C78
dc.w $3EF8, $3FF8,
$0380, $0380
dc.w $0380, $00 00 , $0 0 0 0, $0000
*** storage for old mouse data and sprite save area
.bss
psave:
ds.w 37
ssave: ds.w 37
savebuf: ds.w 133 * enough for 4 bit planes
.end
If you position the mouse pointer over the sprite while
it's moving, a bit of residue will be left on the screen. That's
because part of the pointer is saved to the sprite's save block,
and restored when the sprite moves on. To avoid this prob
lem, try hiding the mouse pointer before undrawing the
sprite, and showing it again after drawing the sprite.
Text
Since text characters on the ST are really drawn on the
graphic screen, dot by dot, text rendering turns out to be an
other special case of bit blitting. The function used to copy a
single text character to the screen is called TextBlt ($A008).
Because there are many variations on text printing on the ST,
TextBlt uses a lot of input variables. The primary line A vari
ables that influence text printing are shown in Table 7-11.
163
To Next Page
Loading...
