Code:


All right so this is my program. In order to run it, your also going to need my WAIT program which consists of this

Code:

E is defined in the program above.

The problem I'm having involves the color commands. When I set the U to become Blue, it stays black and the block next to it becomes blue. So does anybody have any idea why this is happening?

I see you're using some strange characters there. I'm unsure if it's the root of your problems, but certain Prizm OS versions that came default on the calculators have problems with locating with colors when these strange two-byte characters are used. A usual fix is to not use any strange characters, unfortunately. However, we can most likely determine if this is the cause if we knew your exact OS version; do you know what it is, and would you mind sharing it?

My prizm Software version says 01.02.02.

Oweng: Have you tried using SourceCoder to interpret the .g3m's of your programs rather than grabbing the .txt's? It can probably render slightly more attractive code, such as the actual symbols. I should caution you that I'm still teaching it two-byte symbols like E6A6, though. That's off-topic, though; hopefully we can get this fixed. Ashbad, he said it was happening with one-byte tokens like "U" too.

Well, it can happen with any tokens if there are strange characters on the homescreen; I think the average guess is that on these nasty OS versions, it treats color commands applied to the homescreen buffer treating all characters as one byte.

Ahh, that makes sense, thanks for the clarification. I heard that there was an older OS version floating around that repaired the issue? I wouldn't mind if Casio got their act together and issued a newer OS that fixes this, though; do you know if anyone has tried contacting them?

01.02.0200 doesn't have the glitch, but just like 01.01.0200, it's not available for download. The only OS that can be downloaded is 01.02.0200, and that one has the glitch. (No, that's not a spelling error.)

How is 01.02.0200 different from the second time you wrote 01.02.0200? Was that perhaps a typo, since you had said that it didn't have the glitch and then that it did?

No, that's what wasn't a typo. There are two different OSes that are named 01.02.0200 for some reason.

The difference between 01.02.0200 and 01.02.0200 is that one was preloaded onto calcs while the other was downloaded. I haven't checked yet which version of 01.02.0200 Casio is currently preloading on their Prizm's so I'll go grab my sister's calc which is only about 2 months old.

I haven't updated since i got it, as the loader is PC only and i'm a mac.

Let's come up with something to differentiate those two; call them 01.02.0200.dl and 01.02.0200.preload, then. Has anyone tried to do disassembly and then diff'ing on the two versions?

No, because nobody has been able to dump OSes from the calc. The downloaded version of 01.02.0200 is the only one that we've been able to look at.

Ah, I didn't really think about that, although it should have been obvious. I'm sure we'll come up with something eventually.