06-02-2010, 11:45 PM
It's a little ironic that I got hold of some proportional printing code just the other day.
And I was working on a routine to put a character anywhere on the screen (any pixel address).
I guess I can probably drop the PropPrint one. a 64 char one is on my hitlist, though.
Edit: I just tried it. Shouldn't it leave at least a pixel between characters? You might want to consider self modifying code sneakiness as well. I used that with putTile.
Instead of poking to bytes:
POKE uinteger @datastore, data
datastore:
asm
defb 0,0
...
...
...
LD HL, (DATASTORE)
I got it to do self modifying code so that it poked it to the line that has:
LD HL, NNNN
It saves storage bytes, actually - and LD HL, NN is 10 T states. LD HL,(NN) is 16.
And I was working on a routine to put a character anywhere on the screen (any pixel address).
I guess I can probably drop the PropPrint one. a 64 char one is on my hitlist, though.
Edit: I just tried it. Shouldn't it leave at least a pixel between characters? You might want to consider self modifying code sneakiness as well. I used that with putTile.
Instead of poking to bytes:
POKE uinteger @datastore, data
datastore:
asm
defb 0,0
...
...
...
LD HL, (DATASTORE)
I got it to do self modifying code so that it poked it to the line that has:
LD HL, NNNN
It saves storage bytes, actually - and LD HL, NN is 10 T states. LD HL,(NN) is 16.