Put this at the beginning of the program to do exactly what you described: Buff(56)->GDB1

Note that allocating to GDB1 won't work if the program is an app, but otherwise it should be fine

Just realloc the variables back. Think of the realloc command as moving around a window. Usually this window is always looking at L1+714. When you realloc somewhere else, the window has moved to look somewhere else, but the data at L1+714 still exists. So all you have to do to restore your original variables is slide this window back to L1+714. Actually, you can just call ReAlloc with no arguments and itll do that for you.

Copy(^oA,GDB1,56)
ReAlloc(GDB1)
code crap
ReAlloc()

That's exactly what the code does (I think). You're not moving the data when you copy it. When you copy it, then there are two places in data with the original variables. ReAlloc just changes where in memory A points to when you put "A" in your code. So in the code I gave you, you can do whatever you want to the vars in GDB1, but once you Realloc() back to the original variable setting, the variables there won't have changed.

Correct me if I am wrong.
So basically, if I do Realloc(L5), then °A=L5, °B=L5+2,... etc and If then I do Realloc(), °A comes back to L1+741, etc ?

Quote from: Hayleia on November 09, 2012, 12:16:05 pm

Correct me if I am wrong.
So basically, if I do Realloc(L5), then °A=L5, °B=L5+2,... etc and If then I do Realloc(), °A comes back to L1+741, etc ?

That's absolutely correct.

Erm, nope, I just reread my post and I made a typo, it is L1+714 not L1+741 -.-°
But yeah, I was asking about the idea, not the figures, thanks for answering