Unfortunately no, chaining conditionals is not possible in z80 assembly. You could try some tricks with moving the f flag into another register and masking it, for example:


Code:
That's pretty awkward compared with just doing:


Code:

Code:


I need to do a series of these jumps/calls based on the results of cphlde, but everytime i do something to a register, aren't the flags changed? Any ideas?

I need to move through the appvar, pointed to by de, until I find a match of de and hl. Then, I need to check the next four bytes of the appvar against the four bytes after hl. If a full match is found, I need to leave that subroutine with de. If one of them fails to match, I need to reset hl to its original value and start checking from the next de.

This is to find a particular user's calc ID for CALCnet in the appvar.

You could restructure it to something like this:


Code:

Oh, yeah. I didn't think of pushing af. Final question of the day...
is there a quick way to make the screen flicker, then return to the state it was in beforehand (can just do RenderGUI to bring back screen)

I think you might have just answered your own question there, unless I'm misunderstand you.

Well, I know how to bring the screen back, but how do I make it flicker?

You want it to flicker as in blank? If so, you can just clear the screen, iFastCopy, then do a RenderGUI:


Code:

Well, I actually wanted to flicker twice (full white, full black, full white, full black, back to old). Using your code, I was able to deduce how that would be done. Thanks. Now, just have to get the searching of info done, then graphics, then were ready for a beta

Presumably you just changed the 0 to an $FF? Actually, if you did it carefully and used cpl to invert the 0 to $FF and back repeatedly, you could do it with a single loop around that code. Searching of info and graphics and beta sounds great to me! Did you find out what you needed to know about SafeRAM areas?

Well, I know that you encourage the declaring of any RAM needed as programs/appvars when using the GUI API. However, the game uses the first 60 bytes of saferam2 (as defined by dcs7.inc), as well as the GUI API and CALCnet, and the main buffer. What area of saferam is left, and sufficient to hold 25 bytes of player data, per player (max of 10 players, total 250 bytes). Can I perhaps go to 20 players and find a saferam to fit that?

That's not accurate. I encourage the use of SafeRAM as much as possible, even when using the GUI API with CALCnet, and only switching to appvars when you're absolutely out of space. Here's what I use in Oblit:


Code:

I need a quick way to render lines and circles. The DCS7_GUI will not suffice for this. Are there other calls/bcalls?

Use the MirageOS routine fastline.
http://dcs.cemetech.net/index.php?title=Fastline

Which is of course part of Doors CS. And if you need a Bresenham Circle routine, I can give you the one from Obliterate.

Kerm, is it fast? Yes, I do need one...if you wouldn't mind.

Edit: I also need some suggestions/coding help with a n x m. Sprite editor. Using the DCS7 GUI API, you set the spinners to the dimensions of the sprite, and then get presented with a simple sprite editor, like the one in the new Axe Paint program. Any ideas??

Yes, my suggestion is that you do that. And yes, the routine for circles is fast; please bug me on SAX or IRC to share it when I'm on my laptop, or just bump this topic.

Bump on the circles routine...

Here's what I used, by Sigma:


Code:

Ok, the last things I need help with:

1. Conceptual help with rendering of an n x m sprite.
2. How many halt/nop's would be needed to achieve a one-second wait?

1. Use iLargeSprite. Width must be in multiples of 8 pixels, and height can be any value.
2. A nop is 4 cycles. On a 6MHz calculator, 1.5 million nops is one second. On a 15MHz calculator, 3.75 million nops is one second. Halts are not good for timed pauses, as they have variable length delay.