I'm confused....
So how does it check collision with the particle and a solid pixel? Does it have an array of particle locations??

EDIT: Could you maybe show me some psuedo code for the particle and how it moves?

EDIT2: I made a similar program to partex 2 for my NXT, and it runs slower than on the calc. But doesn't an NXT have a faster processor (or maybe not)? The NXT's processor is newer and is running at 48 Mhz,and is 32-bit.

Hmm... On my NXT I did something similar and it is slower...

With very little time to code for Grammer (school and TI-Concours) I don't have much of an update to offer. However, I do these two features for the Text( command that I thought might be useful:

Setting the coordinates:
Text(Y,X with no extra argument will set the coordinate position
Relative coordinates:
Text(+Y,+X,... Grammer now preloads the last text coordinates in Ans before reading the argument. That way, if you want to do something like superscript or subscript, you can do +2 or -2 or something for the Y coordinate. Then directly after, you can set the coordinates again. So as an example:
ClrDraw            ;Clears graph screen and sets text coordinates to zero
Text(2,,"ax        ;Displays text at Y=2, leave X unchanged
Text(-2,,"2        ;Draws the 2 as a superscript (though really, you could use 0 instead of -2 in this case)
Text(+2,,"bx+c     ;Draws the rest back down 2 pixels
As a note, that is minus 2, not negative 2. Also, you see the trick that is new for Text( where you have no argument between the commas. That is essentially "+0" and was not a trick previously available.

Anyways, I am wondering if this is okay for folks?

EDIT: Also, read two posts below before downloading this. I plan to have another release later today with a lot more features than this.

Hmm, I'm not sure, but it does definitely help text graphics. Pretty much, the Text( command has its own section/chapter thing in the tutorial because it has soooo many things that can be done and so many manipulations.

I am also working on a third font option that will use 4x6 font, but it will draw to pixel coordinates. That way, you can combine the variable size font with the fixed font to get better math looking results. I was also thinking of letting the Text( command with no arguments return the current cursor position. I was thinking also of adding the ability to do something like →AB where B would be loaded with the results of Ans and A would be loaded with Theta'. That way, you could do Text(→XY to get the X and Y coordinates in X and Y and also get overflows into other vars. For example, 348*567→AB would load the upper 16-bits of the multiplication to A and the lower 16-bits to B. Finally, I was thinking of adding a new syntax where instead of using A', you can use lowercase A, as well to mean the same thing. That might also cause less clutter in the program editor, too, if you can do →a instead of →A'.

Also, I plan to add all this today.

EDIT: Displaying the small fixed size font at pixel coordinates is now able to be done. This outputs with OR logic as a warning. You will need to do Output(2 to access this method.
EDIT2: Text( without arguments now returns the coordinates as Ans=Y, Theta'=X
Also, you can now do things like →AB
EDIT3:→a is now a valid way to do →A' (Still not able to use lowercase anywhere else in place of primes)
EDIT4:Now you can do math with the lowercase letters instead of primes and use them as arguments

Yes, it is  I am waiting for the "Latest Grammer Updates" thread to be unlocked because an admin locked it >.>

Anyways, so →AB is useful when a function returns info in theta', too. For example, like above, multiplication returns the 16-bit overflow in theta', so if you want it all in one 32-bit number, just use two vars. Plus, now you can do something like A*B→aA.

Anyway, for now, here is the app (have fun!)

Ooh.
Is the syntax for arbitrary tangent same as the other's? (Extra syntax, I mean)

Nice update Xeda. And I assume the text updates are mostly for custom Input routines, right?