Difference between revisions of "Talk:Z80 Routines:Graphic:Bub4font"
From WikiTI
m (Talk:Routines:Graphic:Bub4font moved to Talk:Z80 Routines:Graphic:Bub4font: unite z80 routines) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 4: | Line 4: | ||
The call to LargeSprite can be replaced by any 8xX sprite routine of your choice, as long as you correctly set the input registers. I just used it because LargeSprite was the only XOR sprite routine I included in the code at the time.--[[User:Dwedit|Dwedit]] 11:41, 28 Mar 2005 (PST) | The call to LargeSprite can be replaced by any 8xX sprite routine of your choice, as long as you correctly set the input registers. I just used it because LargeSprite was the only XOR sprite routine I included in the code at the time.--[[User:Dwedit|Dwedit]] 11:41, 28 Mar 2005 (PST) | ||
| + | |||
| + | Yes, we should put a common header to each routine, like the input/output, size, maybe the number of cycles, the author(s), and maybe the calculators it works on (although well designed routines are meant to work on every z80 calc). | ||
| + | |||
| + | |||
| + | [[User:Guillaumeh|Guillaumeh]] 22:54, 28 Mar 2005 (PST) | ||
Latest revision as of 12:50, 25 October 2009
We should have a blurb at the top of each routine page stating what calculators they work on.
--AndyJ 07:43, 27 Mar 2005 (PST)
The call to LargeSprite can be replaced by any 8xX sprite routine of your choice, as long as you correctly set the input registers. I just used it because LargeSprite was the only XOR sprite routine I included in the code at the time.--Dwedit 11:41, 28 Mar 2005 (PST)
Yes, we should put a common header to each routine, like the input/output, size, maybe the number of cycles, the author(s), and maybe the calculators it works on (although well designed routines are meant to work on every z80 calc).
Guillaumeh 22:54, 28 Mar 2005 (PST)
