Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - unknownloner

Pages: [1]
1
Axe / Did I permanently 'break' my calculator's data editors?
« on: June 10, 2013, 05:11:33 pm »
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

2
Axe / 65535->r6 results in r6 being 0? (Solved)
« on: March 31, 2013, 04:01:56 pm »
Code: [Select]
If r4!=r2
 r4<r2?65535,1->r6
End
FnOff
Disp r6>Dec,i,r2>Dec,i,r4>Dec,i
Repeat getKey(15):End
FnOn
The code above is called within a subroutine. When r4 > r2 is displays r6 as 1. However, when r4 < r2 is displays r6 as 0. In my code I displayed r2 and r4 to make sure that they weren't actually equal. I have a draw interrupt for greyscale:
Code: [Select]
If DrawC++=2
 DispGraph^^r^^r
 0->DrawC
End
Would this be changing the value of r6?
I also tried creating a custom variable and locating it towards the middle of L1, and then using that. That also failed. What am I doing wrong? :banghead:

Pages: [1]