.autoregion broken on latest version of armips.

[Gh0stBlade]

.autoregion broken on latest version of armips.

[unknownbrackets]

To be clear, did this previously work (i.e. before #205), or are you not sure if this ever worked? These allocated regions are new, it's possible they have interacted with importobj incorrectly from the start.

In this example, how big is the object? How much data is inserted? You can log this by checking .notice toHex(org(), 16) before and after the .importobj ....

-[Unknown]

[Gh0stBlade]

Ok so upon further investigation, I have managed to solve this issue. The solution simply stores the value of org() in a label and sets the .org back to that old value after .org is changed in one of my includes. This is what appeared to be causing glitches within armips latest version (i changed org to patch a function but didn't restore it whilst it was inside .autoregion). It seems that the older versions of armips prior to #205 did not require this type of solution but i'll stick with it anyway.

[unknownbrackets]

I suppose we could issue a warning if you try to change org inside an autoregion... restoring it ought to be fine, but leaving it changed ought to have broken things before too.

-[Unknown]