KermMartian wrote:
1. Depends what you need. If you've used TI-OS routines to draw on the graphscreen, there's no guarantee that it's in RAM anywhere. If you've used things like DCS and Axe routines to write to the display, you can copy 768 bytes from gbuf through gbuf+767.
gbuf, even if I'm storing the LCD? And where is it in AXE?
ACagliano wrote:
KermMartian wrote:
1. Depends what you need. If you've used TI-OS routines to draw on the graphscreen, there's no guarantee that it's in RAM anywhere. If you've used things like DCS and Axe routines to write to the display, you can copy 768 bytes from gbuf through gbuf+767.
gbuf, even if I'm storing the LCD? And where is it in AXE?
Ok, is there also a way that I can perform a Pixel Test on all pixels on the screen and return a binary string, representing each pixel, then package a binary <--> hex converter routine in.
ACagliano wrote:
Ok, is there also a way that I can perform a Pixel Test on all pixels on the screen and return a binary string, representing each pixel, then package a binary <--> hex converter routine in.
Err, you just copy the 768 bytes from gbuf, that's the same as performing a Pxl-Test() on each pixel and packing it all together.
OH. Ok. I misunderstood that.
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.
»
Go to Registration page
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
