P.s. I know C is already used elsewere, that is likely to screw it up but i tried to insert a cntr byte by doing:

Code: [Select]

cntr: .db 0but then every time I did this:

Code: [Select]

LD cntr, Cor this

Code: [Select]

LD (cntr), Cit threw a error saying: "unrecognized argument"

The reason that's not working is that the only 8-bit register you can store into/from an immediate address is A.  One way you can get around this is by making "cntr" two bytes instead of one, and then using "ld (cntr), BC".


I also see a few issues with your code, so let's try and tackle them one at a time   (The cool thing is that one of them sort of fixes itself and doesn't actually cause a visible problem )

- The first is where you put xpos, ypo, and clip_mask.  Although in this case it isn't a problem, under most circumstances it could lead to quite annoying behavior
  It's best to put variables like this either at the end of your code or at least somewhere it won't be executed (in the Asm28days example, notice that ypos/xpos/sprite are skipped because of the jr's).  The reason for this is that a db/dw directive will actually insert the numbers into the code.  Even though the programmer knows they just want to use those locations as storage, the processor will still try and execute it as code.  In your case the three consecutive $00's are executed, but since this is the opcode for 'nop' nothing happens.

- The next issue are those "push BC"'s you have.  When you use "call", the address of where to return to is pushed onto the same stack as when you push/pop the 16-bit registers.  This means that when you use "ret", whatever is at the top of the stack is popped and used as the address to return to.  There are a couple places where this will cause a problem:
  1) When running through "KeyLoop", you have BC at the top of the stack so when it gets to the "ret z" it starts executing code starting at the value of BC, which is probably not even part of the program.  You need to be careful when using the stack and make sure there aren't any conflicts with call/ret. 
  2) In PutSpr, the first line is a "push BC" and I don't see any "pop BC"'s before the first ret, so weird things are going to happen there as well.
  I think the best way to fix these problems for your program is to just use some memory location for "cntr" instead of the stack.

I hope this helps   I'm not sure if I got all the bugs, but my computer is being mean to me today so I can't test this on an emulator.

lol epic fail on your teacher's part

The disturbing thing is... what part was too complex for him?  The only real differences are the two lines
cout << header + 10 * offset << ':' << string << '\n';
offset = (offset + 1) % 5;The first is fairly straight forward (display "{something}: {what you retrieved}"), and the second is just making "offset" go 0-1-2-3-4-0-1-2-3-4...

[edit] Now that I think about it, for my mathematical software survey ("SoftSurv" for short ) final project my code had a lot of tricks like that.  I wonder if that's why I got an A in the class (my code was completel crap lol)

You scared me! I really thought you quit Omnimaga. Glad you're staying!
And good luck with school. Hope you won't be buying a time-travelling machine to be able to attend your lessons/work/whatever-else-you're-doing-extra.

I shouldn't need that.  Once I chose classes I went to talk with each professor to make sure the workload wouldn't be god awful.

And congrats on making staff Silver Shadow!

I'm not dead!, and as the title says, that's the case

Thanks everyone for all the good luck, though it sucks that I'm just now reading this *after* all the crappy things happened  

Sounds good.  I especially like the penalty for running, even though I tend to abuse running from battles in many games.

This looks great Quigibo

Welcome to Omnimaga, and feel free to introduce yourself in our Introduction forum.

"much better interoperability with TI-Connect"

Does this mean both of them will work simultaneously?

I believe he means files retrieved using TI-Connect can be sent using TiLP and vice-versa.

Very nice calc84! Project M is somehow getting even better   I especially love the animated tiles.