How is this interrupt friendly?  Don't interrupts use af', or am I missing something?  Can you explain it to me?  I sense some clever coding.   TIA Runer (or anyone who beats him).

Before I begin, let me clarify something about shadow registers, because I was a bit confused about this myself for a while. When exchanging registers with shadow registers, the processor doesn't move values from the active registers into the shadow registers and vice versa. There is not one specified set of "active" registers and one specified set of "shadow" registers. Instead, the processor uses a mux to simply flip its definition of which set is the active set and which set is the shadow set. So when an interrupt activates, the processor simply designates the set of registers it wasn't previously using as the set that the interrupt will use.

Anyways, the reason the grayscale routines cause problems is because they require both sets of the af register pair. When not inside an interrupt this is fine, because nothing else was using the second af register pair. But during an interrupt, the af register pair that was being used before the interrupt probably has data in it that we don't want to destroy. However, because the grayscale routine uses both of the af register pairs, this saved value for af will be destroyed. My solution was to back up the saved af register which we don't want destroyed by putting it onto the stack at the start of the routine. At the end of the routine, it is then taken off the stack and put it back into the inactive af register to live to see another day.

Runer, my custom interrupts don't use the shadow registers for af.  They push and pop af instead specifically for the purpose of making the grayscale routines compatible inside interrupts.

Mayhaps it wasn't updated?
It only became compatible with interrupts a few versions ago. I think 0.4.5, but I could be wrong.

Feature request: Backing up programs from archive?

I know this has been requested before, but today I really needed it, huh. break and continue functions. This topic is >117 pages long and can't check'em'all, but did Quigibo said anything about implementing them or not?

Before I begin, let me clarify something about shadow registers, because I was a bit confused about this myself for a while. When exchanging registers with shadow registers, the processor doesn't move values from the active registers into the shadow registers and vice versa. There is not one specified set of "active" registers and one specified set of "shadow" registers. Instead, the processor uses a mux to simply flip its definition of which set is the active set and which set is the shadow set. So when an interrupt activates, the processor simply designates the set of registers it wasn't previously using as the set that the interrupt will use.

Thank you so much for this explanation!  Runer   

Hello, I was trying to make a Pause screenie that made Shade (10) for a while. After that it made shade 45.

However, I want it to make Shade the same number as it was when the program ran, so the user's original shade. I don't see how to do this.

If I can, how?
If not, could a GetShade() like command be implemented?

Seconded on this one.
I refuse to update the user's contract without resetting it after use

And, FFth post