Author Topic: Undocumented BASIC tricks (TI83/84 series) (Read 19145 times)

Spellshaper · « **on:** April 24, 2006, 12:25:00 am »

I think it's time to collect them all again :lol:

later I can gather them and store them into one nice post

me starts off with:

---

Kill "Done"
Kill the pesky "Done" at the end of your BASIC program by entering the following code as last line:
c1-->

CODE

ec1:Output(1,1,"c2

ec2

---

-=removed, the px function is well documented in the manual last time I checked=-

---

Using Complex numbers
Utilizing complex numbers to minimize variable usage:
Complex numbers have the following properties:

-Positivity/Negativity or real number (boolean)
-Integer part of real number
-Decimal part of real number
-Positivity/Negativity of imaginary number (boolean)
-Integer part of imaginary number
-Decimal part of imaginary number

commands to get these values:
-real( (ok, xLib may interfere with this, so this is unusable while also using xLib)
-imag(
-iPart(
-fPart(

using these properties of complex variables in the right way can substitute the usage of six real variables!

---

Krid · « **Reply #1 on:** April 24, 2006, 12:38:00 am »

c1-->

CODE

ec1Text(-54125+1,X,Y,"Text herec2

ec2
To use homescreen font on the graphscreen

tifreak · « **Reply #2 on:** April 24, 2006, 01:09:00 am »

http://s4.invisionfree.com/TIFreakware/index.php?showforum=60

That is all that needs to be said.

DJ Omnimaga · « **Reply #3 on:** April 24, 2006, 01:59:00 am »

we need to repost them here as well, maybe I could find some tricks in the google cache

Radical Pi · « **Reply #4 on:** April 24, 2006, 11:29:00 am »

Erasing 'Done' is easier with c1-->

CODE

ec1"c2

ec2

BCTurk · « **Reply #5 on:** April 27, 2006, 05:16:00 pm »

xLIB Check
c1-->

CODE

ec11
real(0
If not(Ans:Then
Pause "xLib Needed
Stop
Endc2

ec2

Will check to see if xLIB is installed or not. We had it before and I think this is the most optimized version...

White lines using "Line("
c1

-->

CODE

ec1Line(x1,y1,x2,y2,0c2

ec2
Credit to CDI, I picked this trick up from ADotRPG...

Zeromus · « **Reply #6 on:** April 28, 2006, 08:47:00 am »

the line one is in the book too I belive

DJ Omnimaga · « **Reply #7 on:** April 28, 2006, 10:22:00 am »

white lines too I think, at least the old ti manual for 83+

Radical Pi · « **Reply #8 on:** April 28, 2006, 10:24:00 am »

The fifth argument can also be a variable, useful in Paint programs with eraser mode...

shadow · « **Reply #9 on:** April 28, 2006, 10:47:00 am »

this one is't mine but it helped me a lot

getkey>G
End

this waits until you press ANY key then continous on, useful for talking in your game

Radical Pi · « **Reply #10 on:** April 28, 2006, 10:54:00 am »

Do you mean Repeat getKey:End? It is useful most of the time.

Another trick I like I used in GQES to boost speed:c1-->

CODE

ec1Repeat (long keypress condition here)
Repeat Ans
(grayscaling code here)
getKey
End
End
Ans->Kc2

ec2The long condition slowed down the loop on every cycle. This way fixes that.

DJ Omnimaga · « **Reply #11 on:** April 28, 2006, 12:26:00 pm »

actually if u want better key detection that can be useful, I did that in reuben quest

Radical Pi · « **Reply #12 on:** April 28, 2006, 12:44:00 pm »

Really? ^^
I'm finally learning something...

I have a nice string searching routine I'll post.

crzyrbl · « **Reply #13 on:** April 28, 2006, 03:06:00 pm »

QuoteBegin-tifreak8x+Apr 24 2006, 07:09 AM-->

QUOTE (tifreak8x @ Apr 24 2006, 07:09 AM)

http://s4.invisionfree.com/TIFreakware/index.php?showforum=60

That is all that needs to be said.

*reads Definition of memory errors

uh oh, does recursion really cause a memory leak?

shadow · « **Reply #14 on:** April 28, 2006, 03:10:00 pm »

sigh, i hate goto's that the number one problem with my game right now (well maybe number two, laziness comes first

)
but so far it kinda works fine right now

Author Topic: Undocumented BASIC tricks (TI83/84 series) (Read 19145 times)

Krid

BCTurk

Zeromus

shadow

crzyrbl

shadow