lol, I changed straightaway from 0.5.3 to 1.0.5

Ah, didn't think about that.  I will add that next version and update the docs.

Could you post the code itself?  That would probably help ferret out the bug quicker

Where is the pointer N coming from?  That might have something to do with the issue

Hmmm, is the appvar archived?  Does this still pose an error if you just type those two lines and compile to application?

Quote from: Builderboy on October 16, 2011, 11:23:45 pm

Hmmm, is the appvar archived?  Does this still pose an error if you just type those two lines and compile to application?

The appvar is not archived. In fact, it is reading correctly from the appvar on  the next line, Copy(N+768,^oC,12)

That copies the data to the variables C,D,E,F,G,H. Is that what you wanted?

Quote from: Freyaday on October 16, 2011, 11:26:55 pm

Quote from: Builderboy on October 16, 2011, 11:23:45 pm

Hmmm, is the appvar archived?  Does this still pose an error if you just type those two lines and compile to application?

The appvar is not archived. In fact, it is reading correctly from the appvar on  the next line, Copy(N+768,^oC,12)

That copies the data to the variables C,D,E,F,G,H. Is that what you wanted?

Yes.

How are you checking whether or not L3 is cleared or not?

ClrDraw
DispGraph^rr

Hmm i can't seem to replicate it, can you replicate it just by using those lines of code like you showed me?

It works fine when I put just those lines into an app. However, there is a lot of other code, including the same line changed only in variable elsewhere (this is a multi-file source wherein the programs are intended to also work as standalones)
However, I checked to see if the peephole optimizations are at fault by pressing ZOOM instead of ENTER, and the same problem occured.