Author: shundra9
Posted: 25 Nov 2012 10:18:59 pm (GMT -5)
Thanks chickendude! I will probably want to analyze the routine a little further, but first I have some logistical questions about the above program:
1) You suggested calling ionFastCopy over bcalling _GrBufCpy. Is there a similar ion routine for clearing the graph buffer, that is perhaps faster than _GrBufClr? Also, is it advised to always clear the graph buffer before using ionPutSprite?
2) The Doors SDK that I downloaded came with several include files like ti83plus.inc, one of which was ion.inc. I was thinking that I might be able to leave out the ionPutSprite code that you gave above if I instead #included ion.inc at the beginning of my source. However, ion.inc appears to contain no actual code, just a bunch of defines and equates. Does this mean that I will need to manually copy the above code into every program where I wish to use ionPutSprite? Also, does the program above need ion.inc at all?
3) Again concerning ionFastCopy, I noticed that your code above doesn't actually have any ionFastCopy label, and there is no code for it in ion.inc either. When I try to run the code on an emulator, the output is just a blank screen from which I cannot escape. Did you just forget the ionFastCopy code or is there a step that I'm missing?
4) Why does the ix register shift to the byte after your sprite label, and what would be in that byte? Is that the first byte containing actual sprite data, or does the ix shift just enable a programmer to quickly output the next sprite in the file, perhaps for animations?
5) Lastly, sort of unrelated, I keep hearing people talk about "safeRAM." Does this term refer to specific areas of z80 RAM or is it just a general term for storing variables "safely" in RAM rather than in the stack or a register?
Posted: 25 Nov 2012 10:18:59 pm (GMT -5)
Thanks chickendude! I will probably want to analyze the routine a little further, but first I have some logistical questions about the above program:
1) You suggested calling ionFastCopy over bcalling _GrBufCpy. Is there a similar ion routine for clearing the graph buffer, that is perhaps faster than _GrBufClr? Also, is it advised to always clear the graph buffer before using ionPutSprite?
2) The Doors SDK that I downloaded came with several include files like ti83plus.inc, one of which was ion.inc. I was thinking that I might be able to leave out the ionPutSprite code that you gave above if I instead #included ion.inc at the beginning of my source. However, ion.inc appears to contain no actual code, just a bunch of defines and equates. Does this mean that I will need to manually copy the above code into every program where I wish to use ionPutSprite? Also, does the program above need ion.inc at all?
3) Again concerning ionFastCopy, I noticed that your code above doesn't actually have any ionFastCopy label, and there is no code for it in ion.inc either. When I try to run the code on an emulator, the output is just a blank screen from which I cannot escape. Did you just forget the ionFastCopy code or is there a step that I'm missing?
4) Why does the ix register shift to the byte after your sprite label, and what would be in that byte? Is that the first byte containing actual sprite data, or does the ix shift just enable a programmer to quickly output the next sprite in the file, perhaps for animations?
5) Lastly, sort of unrelated, I keep hearing people talk about "safeRAM." Does this term refer to specific areas of z80 RAM or is it just a general term for storing variables "safely" in RAM rather than in the stack or a register?