So I was messing around with TI-OS lists in axe, and ended up overwriting what I assume is some kind of tail sequence to mark the end of the list. When I went into my ram it then said the list was taking up all available ram. Well, I wiped my ram which seemed to mostly fix the problem, but now any time I run Axe, after closing axe my data editors will break. I don't know if this is directly related to me messing with the lists, but it started happening around the same time so I assume it is.
My list editor looks like this:


My stat plots screen looks like this:


My matrix editor looks like this:


My function editor looks like this:


and my table screen (2nd + graph) looks like this:


Interestingly, running Doors CS fixes the editors, as does wiping my ram. SetUpEditor does not fix it though.
It looks like a problem with some sort of OS flag actually, because after viewing these screens, if I go to my graph screen all the text that should have been in the editor screens are on the graph screen. It's drawing the text to the graph buffer rather than the screen. In fact, after using a BASIC Text( command on the graph screen, the editors work again properly. I've tried everything I can think of to make it stop doing this. I've wiped my ram, archive, and entire calculator. I've put a freshly downloaded version of axe on it with nothing else, I've even tried re installing my operating system. None of these have fixed the problem. Is this a bug with axe that I never noticed before? (Been using this version for awhile now, never noticed it before). I'm using 1.2.1. is there anything I can do to stop it?

EDIT: Using a TI-83+ Black

Unfortunately ram clears are only a temporary fix. I made a quick axe program to reset all text flags to default, and running that fixes the problem temporarily, but the problem comes back if I run the Axe app again.

I'm on v1.18 OS. Don't remember if my calculator came with 1.17 or 1.18, but I haven't updated to 1.19

Perhaps try deleting the AxeData appvar? Then clear RAM, check that lists and stuff work, run Axe and immediately exit, and check the lists and stuff again.

I have a feeling that this problem didn't only just recently start happening, but that you only recently noticed it. I just tested Axe 1.2.1 on my 83+ and I have the same issues. Apparently I messed up some aspect of 83+ compatibility in 1.2.1 or 1.2.0. I'll try to pin it down today.

EDIT: No need to pin it down, it seems. I already replaced whatever the buggy code was a while ago and thus inadvertently fixed the bug while making improvements for the upcoming Axe 1.2.2!

I kept having this problem when I used a beta version of Axe 1.2.1.
Axe is quite the app, but it can be dangerous. I semi-bricked a calc with that version of Axe. If you try to go to an error in the prog editor straight from it, it will cause buggy things to happen. It won't usually crash right away.

Quote from: Dapianokid on June 12, 2013, 03:06:08 pm

If you try to go to an error in the prog editor straight from it, it will cause buggy things to happen. It won't usually crash right away.

Yeah I have this issue too, though zStart's compilation shotcuts fix it. The thing is when you run into it it causes all of your free RAM to be leaked and forces you to reset.

Can you elaborate? I'd love to fix bugs that have plagued users, but I have to know about them first.

EDIT: Can't seem to replicate the issue in a few quick tests, so more information would help. The absolute best thing you could provide is a ROM file (via pm, don't post ROMs publicly!) with instructions on how to recreate it, but I'll work with whatever information you can provide.