Yeah, I don't think that was his real code since its an infinite loop on top of that.  I initialized A and changed the "While 1" to "Repeat getkey(15)" when I tested this I should mention.

Quote from: Quigibo on June 15, 2010, 05:03:56 pm

Are you sure Str2 is exactly 10 characters?  Maybe you mistyped it.

OnMode

wow didn't even know that and I used Mirage for almost a decade

Is it safe, though?

As long as you have interrupts enabled, and don't write data over the L2 free ram, then its safe to use.  But it doesn't save you from buffer overflows or corrupting ram of course.

What I'm curious about is the opposite.  If you disable interrupts, can you use L2 ram area in mirage? (All the DispGraph routines re-enable interrupts so immediately disable them after those).

Yeah, that sounds right. By the way, if you want, you can add some simple code to preserve interrupt state. Having interrupts enabled for even one microsecond can cause disasters.

Start your routine with this:
ld a,i
push af
di
and end it with this:
pop af
ret po
ei
ret

Oh, wow!  I'd never heard of On + Mode.  That should help me if I get infinite loops in Mirage.

Calc, how does this line work?

ret po

Thanks.

Okay, first thing, Axe Tokens.  Enable and disable them with Alpha+Vars.  If the screen flashes, you know they have been toggled.  The current token remapping is this:

conj <-> Copy
Expr <-> Exch
SinReg <-> Freq
det <-> Zeros
int <-> sign
>Frac <-> >Char
deltalist <-> Data
Repeat <-> Until
Tangent <-> Bitmap

Let me know if you all like it.  I might decide to make it  quote unquote 'Mandatory'.  Like the code would be pretty unreadable without it.

I modified my RPG demo to use subroutines if you want to look at it.  Basically, you call it with up to 6 arguments and then in the subroutines, the arguments turn into r1 through r6.  Do not use subroutines with arguments in subroutines with arguments otherwise there could be conflicts since they all share these values.  While these new variables can be used outside of subroutines, it is discouraged because they get erased every time you call a subroutine with arguments.

EDIT: Oops, I just realized I accidentally switched Fill( with Zeros( instead of det(.  I'm releasing another version soon to fix stupid typos like this.  I think that will be the pattern from now on.  Big improvements followed by corrections.  I'll wait to see what other corrections need to be made first of course.

Ooh, base 2 logarithm/exponent can be useful for a simple floating-point implementation.

Come to think of it, to improve the usefulness of fixed-point values (see: sin/cos), you should make an alternate multiplication routine, "**", to multiply two numbers but return the top 16 bits of the 32-bit result. Currently, there is no easy way to do that.

A little more explanation on your Tangent command please?

Is width in pixels or bytes? If it's not a multiple of 8 pixels, do you pad the last byre?