0 Members and 1 Guest are viewing this topic.
Nope, just that. But you have to make sure to add the Fix 8 to the end of the program. It makes the calc draw bitmaps directly to screen, like normal.
It would also be able to read/write to bits instead of just bytes and nibbles.
Quote from: Michael_Lee on February 14, 2011, 02:59:51 pmNope, just that. But you have to make sure to add the Fix 8 to the end of the program. It makes the calc draw bitmaps directly to screen, like normal.Question: At which point does the calc ever actually use the bitmap command I wonder? O.o
Bit flipping sounds like a useful feature too. Might be slow, though.
Whoops, I just noticed I replied to ralphdspam on a different page...
And now that I think of it, when would you use SET and RES in an Axe program, then? Especially considering the way Axe does math.
Something like the multi-digit Fix things would be cool in a normal program as well (something like Fix 0,6,8).
Quote from: Darl181 on February 19, 2011, 12:04:39 amSomething like the multi-digit Fix things would be cool in a normal program as well (something like Fix 0,6,8).or Fix 068 could work. I believe that was asked before somewhere. I like the idea. Would it be smaller compiled code?, or the same?
Quote from: ralphdspam on February 15, 2011, 01:39:56 amIt would also [like to] be able to read/write to bits instead of just bytes and nibbles. You can, with bit-masking. (Use and, or, and xor to mask bytes, then store them back.)Bit flipping sounds like a useful feature too. Might be slow, though.
It would also [like to] be able to read/write to bits instead of just bytes and nibbles.
179->AFor(B,0,1)If nib{A*2+B} and 8Sub(D)EndIf nib{A*2+B} and 4Sub(D)EndIf nib{A*2+B} and 2Sub(D)EndIf nib{A*2+B} and 1Sub(D)EndEndLbl D.Do StuffReturn
179->AFor(B,0,7)If bit{A*8+B}.Do StuffEndEnd