0 Members and 1 Guest are viewing this topic.
Quote from: Freyaday on June 01, 2011, 05:04:45 pmOh. That's why that area contains the flag for whether or not ON was pressed!There's a good chance you went past the end of saveSScreen. End of saveSScreen = $89EB. System flags = $89F0.
Oh. That's why that area contains the flag for whether or not ON was pressed!
Ah, yes, that makes sense. If the calc APDs, then the current screen has to be stored somewhere. This area is appropriately named the "saveSScreen." Unfortunately for you, this is L1 in Axe. Basically if in your program the calc APDs, then you cannot use any of L1. Remember that Axe Vars are stored at the end of L1 (as it's actually 768 bytes if you reallocate the vars).Here's your fix:1. Use #Realloc() to change the location of the Axe vars to some other place, such as L4.
#Realloc(L2)
2. Never ever ever use L1 in your program.Good luck!
Yep, APD stores the screen to SaveSScreen. Maybe someone should tell Quigibo to add in a bcall(_disableAPD) command.
Great! Just watch Iodine, I believe it's molar mass is .01 too high because on the old table I got them from, that's what it rounded too. So I'll have to change that. You would look a little silly if you got the molar mass of something wrong
So to fix, would I simply put on the top:Code: [Select]#Realloc(L2)...and continue to use my regular Axe variables fine, just in a different spot?
Yup, only I'd use L4 or L6, as you can't run programs that use L2 from Mirage.
L4 = 256 bytes (tempSwapArea) Volatility: MED (Corrupt when archiving/unarchiving in program)L5 = 128 bytes (textShadow) Volatility: MED ("Disp","Output", and "ClrHome" will corrupt)L6 = 768 bytes (plotSScreen) Volatility: HIGH (Any buffer drawing will corrupt)
L3 = 768 bytes (appBackUpScreen) Volatility: MED (Saving to back-buffer will corrupt)
Zeros(54)->GDB0#Realloc(GDB0)
Whoops, I meant L4 or L5. In your case, I'd also suggest doing this:Code: [Select]Zeros(54)->GDB0#Realloc(GDB0)(This only works if you compile it as a program, not an App.)L5 would work if you don't use Disp, Output, or ClrHome.
What does the above code do? This seems to be a... wait, program writeback storage? O_O
Is there a way to view a list of what's assigned to what on+num shortcut? Like, calcutil has a program it reads from, which can be edited through the TIOS editor. If not, there's another feature request for ya
Also, might it be possible to ON+ENTER compile from the homescreen?
Author
Topic: zStart - an app that runs on ram clears (Read 333467 times)
