[TI BASIC] Optimizing

merthsoft · Post by **merthsoft** » Wed 30 Mar, 2005 9:25 pm

Hey, I edited that post to say it didn't... crap, AOL is evil...

MooK · Post by **MooK** » Thu 31 Mar, 2005 3:11 am

I guess this maybe deserves some testing...

That_One_Guy · Post by **That_One_Guy** » Wed 06 Apr, 2005 2:29 am

Hey, I was wondering what the fastest GetKey routine would be? I use

:DelVar A
:Repeat A(not equal)0
:GetKey->A
:End
:If A=21
:do this
:if A=31
:do this

and this is really slow. I'll post some more bits of code i need optimized. Thanks in advance!

DarkerLine · Post by **DarkerLine** » Wed 06 Apr, 2005 9:17 pm

Repeat Ans
getKey->A
End
If A=21:Then
...
End
If A=31:Then
...
End

if you only need the key once and don't have to save the keypress:
Repeat Ans
getKey
End
If Ans=21:Then
..2nd pressed...
Else
..other keys pressed..
End

if you don't need the key at all and just want to wait for any key:

Repeat getKey
End

That_One_Guy · Post by **That_One_Guy** » Wed 06 Apr, 2005 11:20 pm

Thanks a lot, every little bit helps. is there a faster way than:

Repeat Ans
GetKey
End
If Ans=24
Y-1->Y
If Ans=25
X-1->X
If Ans=26
Y+1->Y
If Ans=34
X+1->X

I seem to recall someone mentioning a faster way, but if not, oh well.

kalan_vod · Post by **kalan_vod** » Wed 06 Apr, 2005 11:34 pm

Repeat Ans
GetKey
End
Y+(Ans=26)-(Ans=24->Y
X+(Ans=34)-(Ans=25->X

That_One_Guy · Post by **That_One_Guy** » Thu 07 Apr, 2005 12:11 am

kalan_vod wrote:Repeat Ans
GetKey
End
Y+(Ans=26)-(Ans=24->Y
X+(Ans=34)-(Ans=25->X

That works, but only the Y one works. The X one doesnt do anything. But other than that, very speedy.

Timendus · Post by **Timendus** » Thu 07 Apr, 2005 12:33 am

Ans is fucked up by the Y statement... you will need to store the getkey value somewhere I'm affraid...

That_One_Guy · Post by **That_One_Guy** » Thu 07 Apr, 2005 12:59 am

No worries, it'll only slow it down a tad bit, if that. And true, minus one variable, but i never use many variables, unless im working on something big. this is just to satisfy boredom. May go big, but doubt it

dysfunction · Post by **dysfunction** » Thu 07 Apr, 2005 4:55 pm

The Y variable has interesting problems with the TI-OS.. I've written several program movement loops wherein Y was randomly set to 0. I think there's some issue between the Ans variable and the Y variable, though I don't know why.

Timendus · Post by **Timendus** » Thu 07 Apr, 2005 5:18 pm

Yes, I had that too... And Q also has some problems; I managed to reset my calc with a basic program getting input in Q once

DJ_O · Post by **DJ_O** » Thu 07 Apr, 2005 5:29 pm

This happens with Y and X, when in Func mode. If you put the calc in another mode I believe this cause problems with other variables like theta, R and P or something, basically all real veriables that cannot be archived. The only way to prevent this is to cleardraw at the beginning of your program, use the Disp command followed with a Dispgraph and every time you need to clear the screen BCALL ClrLCDFull using Omnicalc execasm function or use an Asm lib to clear the screen

merthsoft · Post by **merthsoft** » Thu 07 Apr, 2005 8:15 pm

Or just don't use X or Y.

Post by **tr1p1ea** » Fri 08 Apr, 2005 2:31 pm

I used to hate that, when X or Y would get over-written for no reason :S.

DJ_O · Post by **DJ_O** » Fri 08 Apr, 2005 2:39 pm

Since I use xLIB instead of ClrDraw to clear the screen I have no more problems in using those vars, altough I still tend to use them in last resort. It's hard in BASIC to deal with 33 variables (A-Z, theta, n, N, I%, PV, PMT, FV) and lists are very slow