well, were is no need for advanced sin/cos-stuff... one can simply use the area of the triangle:
A = (50 * h)/2 = 30*40/2
which leads to h = 24, if i'm not mistaken

And here I was, about jump straight in with law of cosine...
Thumbs up for simplicity!

It does that: I'm starting to get a bit annoyed.

It's up now, though.

Is there a reason to keep this thread stickied?

Just wanna check before I unsticky it.

It just occurred to me that this is the wrong thread: questions about Axe belong in the Axe language subforum.

Therefore, this topic has been moved to Axe Language.

http://ourl.ca/10745

Ah.  Avoid using Input.
It uses the built-in input routine provided by TI-OS, so you get to use all the menus, and stuff, but there's nothing that prevents the user from hitting 2nd-quit and terminating your program in the middle of something.  You should probably make your own input routine, instead.  It's a major hassle, but it's safer.

Let's say that you want to treat the appvar as a matrix with 5 columns and 4 rows.  For the most part, memory in Axe is treated as a list, not a matrix, so we have to use a workaround to be able to use memory as a matrix.

So, we want a matrix.  Because our matrix has sides of 4 and 5, the total amount of memory we want would be 20 bytes (or 40, if you use double-byte numbers).

We can create an appvar like this:

"appvNAME"->Str1
GetCalc(Str1,20)->P
You can get the 'appv' symbol by hitting [2ND] then [8].

To write to and access the 5th byte in the appvar, you would do this:
42->{P+4}
Disp {P+4}>Dec
(Remember that lists in computers start at zero: to access the 1st byte, do {P}, which is equal to {P+0}, and to access the last, 20th byte, do {P+19}).

However, if we chose to treat the appvar as a matrix, we can.  The appvar won't be changed in any way, all we're doing is changing the way we access it.
I'm going to arrange the bytes in a block.
00  01  02  03  04
05  06  07  08  09
10  11  12  13  14
15  16  17  18  19
If we conceptualize the appvar like this, then we can use a short formula-thingy to input the row and column, and return the actual byte we want.

{ROW*LENGTH + COLUMN + POINTER}

So, if we want the byte at column 1, row 2, we would do this:
{2*5+1+P} == {11 + P}
Because this is computers, we treat the first rows/column as the zeroth row/column.


That might be a bit of a complicated answer: let me know if you need anything clarified.

Hello: if you notice, the last post on this thread (before yours) was on February 28th.  Your response was today, May 1st, which means that there is almost a 2 month gap between your post and ztrumpet's.  When somebody responds to a post that is older then 3 weeks (which is called necroposting) without really adding anything, it's considered rude.

In the future, please note the date of the previous post before choosing to respond.  Thanks!