Grammer 2-The APP

[Xeda112358]

Hmm, new update here. I have added in a better ability to change specific modes using Fix and you can now use StorePic and RecallPic. Even better, though, is the updated particle command ^_^. It now gets about 5.66 FPS with Partex2 and 2048 particles instead of 3.60 and you can customise the rules a little For example:

Code: Select All | Copy To Clipboard

1 2	P▶Ry(2,"D,LR,U

That sets the rule to check the down direction first, if it cannot move down, try left and right, if that fails, check up

[C0deH4cker]

You should consider changing your version structure to be VERSION.YEAR.MONTH.DAY so that the version is always going up, not up and down.

[Xeda112358]

Yeah, I realised that in hindsight It does get confusing I will definitely do it that way for Grammer 3

[persalteas]

I steal your screen to use it in the news on TI Planet

[Xeda112358]

Hehe, I saw It's no problem

[persalteas]

Questions relative to your updates:

1) using StorePic or RecallPic : I suppose it's for the OS variables, it's not pointers ?
It it posible to store a specified buffer with StorePic ?

Maybe

Code: Select All | Copy To Clipboard

1 2 3

:Disp piXXXX :StorePic 1

?


2) P▶Ry(2,"D,LR,U  is exactly the same as P▶Ry(2,2145 ? So why did you implement 2 syntaxes ?

[Xeda112358]

1) using StorePic or RecallPic : I suppose it's for the OS variables, it's not pointers ?
It it posible to store a specified buffer with StorePic ?

Maybe

Code: Select All | Copy To Clipboard

1 2 3

:Disp piXXXX :StorePic 1

That code should work

2) P▶Ry(2,"D,LR,U  is exactly the same as P▶Ry(2,2145 ? So why did you implement 2 syntaxes ?

It is because number are easier to modify than strings. However, using a string like that is much easier for the programmer. Also, the letters correspond to Down, Left, Right, Up.

[persalteas]

Okay, thanks.

Hmh... You said you added features to Sprites and Circles (29/04) what did you add ?

[Xeda112358]

Oh, I made some arguments optional. For example, Circle(Y,X,R[,T. It automatically uses option 1, now. For the sprites, you don't need height and width if it is a regular 8x8 sprite.

However, if you need to add other arguments (like a buffer), you will need to have all the arguments before it.

EDIT: Also, I just realised that I will have to make one more update because I broke the feature to run Assembly programs.

[persalteas]

Okay. I'll update my tuto, with these version of Grammmer, with the Hooks names , and the beginning of the second part.

[Yeong]

@Xeda:

For the fire animation, can you add an optional argument to display the different direction of fire buring? (eg default burns upward. )

[Xeda112358]

Hmm, I might be able to do that

[Xeda112358]

Unfortunately, I do not have the downward flames available, but I hope this update is as awesome as I think it is

Things I have added or fixed in Grammer 2:

• Fixed the RecallPic token to work with archived pictures. I have also documented the extra arguments for RecallPic and StoPic. As a warning, RecallPic will destroy the data at 86ECh (saveSScreen).
• pxl-Test(' has been removed and it has been replaced by a new rectangle option. This works faster and better as it piggybacks off the updated clipping for rectangles.
• Rectangle clipping is in all directions and allows for some negative coordinates.
• The line drawing routine now supports some minor clipping off the bottom and right of the screen. It is now slower drawing about 500 lines per second as opposed to 625.
• solve(5 lets you write to a port and solve(6 reads from the port. This requires some more advanced knowledge of the ports, but if you know what you are doing, you can do things like use the link port for linking. Honestly, though, this is still proving difficult for me. I have managed to send a two byte value over the IO port.
  
• IMPORTANT: Grayscale has changed and some backwards compatability is broken. It now works automatically in 4-level grayscale. There are 12 modes, two of which are the same (3-level gray), so I hope it satisfies folks! By default, it uses 50-50 mode, so it takes 50% color from each buffer. Pixels need to be ON in both buffers for it to appear black. Before, as long as it was on in just the black buffer (now the primary buffer), it would appear on.
  
• Input now works very well. Only keys that map to a token will return a token (for example, ON does not register as a token and the arrows don't). [Del] and [Clear] will work as a backspace and it will delete the whole token, not just a space. It also allows you to use a short string as an argument. This string will be used to close the input. For example, ")" will make your input close with a ")" at the end. Finally, your input will be highlighted as you input. Some example code:
  
• L (the list L), can be used to execute a specific line of code. I was thinking of making a programming language based on this command, actually.

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10

.0:Return ClrDraw Text(°"(x,y)=(           ;ClrDraw sets the cursor to (0,0), so I can use ° expr(Input ",)→X         ;I get the next input here. The string is ,) Text(,+1                 ;This increments the X coordinate. expr(Input ")→Y          ;This gets the Y value. Pxl-On(Y,X               ;Or whatever you want to do with the coordinates. DispGraph Stop

• There is now a mode for displaying signed numbers when using Text(
• The rectangle routine is now slightly faster, drawing about 1.75 more rectangles per second.
• Made the number conversion routine (for storing to OS real vars) smaller and faster. It now takes at most 666 cycles instead of 750.

[Sorunome]

Wha, that is some very cool feature! I like it!

[Xeda112358]

For the curious, here is what grayscale now looks like (it is not quite what it looks like on an actual calc, though >.>
6MHz:
15MHz: