Ug...tell me about it...I had some of the worst memory leaks on hunt, and it took me forever to fix them
the random error tat isn't an error usually comes up with me if prgmLOL is exsisting, so deleting it before compiling will usually keep it from happening, but sometimes it won't.
Hmm, how hard would it be to add something that when it errors it tells you what line it's on?

Yeah, well I did that because there are issues with installing there in vista/7...but I guess I could.

Thanks!
Yeah the DOM inspector addon is reliable, it's helped me solve every problem so far without it I would have a hell of a lot harder time debugging
the only thing it can't help me with is opening/saving files due to the fact that it isn't allowed to do that in firefox...for some odd reason...

ok, another nightly uploaded, this one now will change the name of the tab to the current file it holds so it's easier to work with, and when you change your file the icon changes to let you know that the work is unsaved, so when you save or open a new one the icon changes back.
please let me know what you think!
http://code.google.com/p/asmdevset/downloads/detail?name=ADE_nightly_win32.exe&can=2&q=#makechanges

ok, so this isn't really a bug, but it's a warning...if you run this code:[0011223344556677]->pic1
7->D
For(C,0,50)
D+1->D
If D=8
0->D
End
For(A,0,12)
For(B,0,7)
pt-on(A*8[+D],A*8+D,pic1
End
End
DispGraph
End(note: [+D] is optional (take out the [] ))
you will with the extra +D on the completion of the program if you go to a menu and then back to homescreen your cursor will change to a insert-2nd one, and then your calc will crash and ram clear, if you exclude the extra +D then you will brick your calc...the same thing happens but instead of a insert-2nd cursor it is a lowercase-alpha cursor. and your calc will not crash but stay on that screen, and I tried pulling the batteries (all of the AAA's) out to no avail.
I was able to fix it though by linking a classmate's 84+ to mine and sending an empty L1 to my 83+, and upon the 84+ erroring because there was nothing receiving, my 83+ on the other-hand unfroze and I was able to do things with it, although the alpha cursor was stuck on lowercase... when I didn't try to clear the ram right away it froze again, and I had to send L1 again. the second time I immediately cleared my RAM and my calc is now fixed.

tl-dr;
don't display sprites off of the screen on the bottom, or to the right by 8 and then quit out of the program, bad things happen...

it should, if you replied to me...

No, the program flow doesn't work well withtye new commands...I need to re-organize it.