I don't seem to fall until I go above the screen

It still don't fall   press second and I go up, but I never fall back down

Okay, cool! I can't wait, it looks cool! At first I thought I messed up Grammer, then I realised that you said it might not be typed right

Feature request:
is there a way so we can use loops within the argument of commands, like:
If Pxl-Test(B+11, For(A,1,7):A:End)

Hmm, I can try to add the seq( command, then. That would do something similar. It might be an ideal notation for algorithms, too..
Also, I think I want to add a For(' command that doesn't modify a var but executes a number of times. For example, For('100 would execute a loop 100 times (this is just an idea)

Another feature request:
Sprite widths of multiples of 4 instead of 8, considering that's how hex works.  I want to clone Tetris and I want more compact codes instead of C0C0C0C0C0C0C0C0... etc.

Hmm, I like the idea, but I am not sure if/when I will add it. However, that did remind me of some features to add...
For example, you guys know how there are custom font hooks and parser hooks in TI-BASIC? What if I did something similar for Grammer? I would try to make sure Assembly programers and Grammer programmers could set Grammer hooks. I was planning on doing this months ago, but I forgot! I even have the fontset enabled to be easily swapped out by a custom one.


Also, just for those who are interested, I plan to add a text mode that lets you draw ASCII... This is mostly because there are chars in the grammer fontset not normally available >.>

So you have a way to make sure the block doesn't go through another block? Then you can probably use a series of pxl-Test( in a for loop to test if a line is complete. If the shape was 2 blocks tall, you only need to test those two rows.

Use the same idea for checking if you lose

As for shifting blocks down, I am not sure how that will work I know I could whip up some code in Grammer, but it would be a little complicated and use several buffers.

EDIT: Okay, here is the complicated piece code I was talking about It took some thought, but I figured it out
Send(768,"VGBuf→K
37696→J
Lbl "SD→I

<<code>>

.SD
Disp K
ClrDraw
Line(X,Y,H-4,W,1
Fill(10,J
Fill(13,J
Tangent(4,1
Fill(13,J
Disp J
Line(X,Y,H,W,0
Fill(9,K
End
The shifting code is at .SD
The inputs to that subroutine are:

X and Y are the upper left coordinates of the place to begin shifting at
H and W are the height and width of the region to shift down
K points to a 768-byte buffer
J points to the main buffer (usually the graph buffer)
I hope that helps!

So the Grammer coders are probably familiar with Partex (or at least the screenies) by now, but it is turning into some cool stuff, I think. So, this is  why I am posting it here. It is a slow moving project (there won't be 3 updates a day ), but it is one that will probably continue for a little bit. Right now, it is like a powder toy. You can do basic pixel drawing and particle dropping, but it is pretty fun!

Right now the controls are:
Arrows are for movement (including diagonal)
[mode] exits
[Clear] freezes all pixels on the screen, permanently
[Alpha] clears all drawing
[2nd] draws a pixel on
[del] draws a pixel off
+/- toggles between particles
[ / ] pauses the particles
[ * ] unpauses the particles

One nice thing is that this program is 314 bytes, so if you have the app version of Grammer, this is really doable! And with the latest app version, you can even keep Partex archived!

Actually, Repeat loops are different from While loops. Repeat loops check the condition after executing the loop and While loops check the condition before executing the loop.

Okay, well I am about to head to class and then directly after I get to go to a math conference (out of state), so I probably won't be able to do much until late tomorrow or the next day, but I will try to get that up and running, too! The first version won't be compatible with other apps, probably