The direction keys rotate; it may be that your grid size is so large the rotation gets super slowed down. Imagine the default axes set up such that negative x points behind your screen, and positive x points towards you, the user. Negative y points left, and positive y points right. Positive z is up, and negative z is down. The left/right arrows rotate around the z-axis, up down rotate around the y-axis, and symb/help rotate around the x axis.

Yup, removing EXPORT before variables makes the variable "super global". I don't know how to say it, but there are three types of variables on the HP Prime:

-Local: Declared at the start of a function, only useable in that function and cleared from memory once returning from the function
-Global: Declared with EXPORT at the start of the program, useable through the entire program. The variable is deleted once quitting the program.
-External: Declared without the EXPORT command, still at the start of the program. This type remains intact once exiting the program and can be used anywhere.

In TI and Casio BASIC, however, we can edit variables as we wish, so people can fake highscores and cheat in long RPGs. Even if only the source HP PPL program has access to a declared variable, can that variable still be edited with an on-calc editor or something? Also another question: When using ON+SYMB or pressing the RESET button, are variables cleared? If so, then is there a way to ensure that variables are reset-proof? Else, this might be a problem for role-playing/adventure games like Legend of Zelda or Final Fantasy. Since the HP Prime isn't that stable, we sometimes have to reset it to bring back normal behavior, and it would suck to have to backup our progress on a computer every two hour or so...

This is incorrect. LOCAL is restricted to inside a BEGIN END; pair. EXPORT makes global variables accessible system-wide. Removing EXPORT creates a variable "global" only to the source file. Programs from a different source file cannot see/use these variables, nor can the user. Whether EXPORT'ed or not, both global types remain and retain their values after programs complete their execution until next compile-by-exiting-the-editor event. An ON-SYMB does not clear global variables (not their existence nor their contents).

http://www.hpmuseum.org/forum/thread-215.html

While a non-EXPORT'ed global variable cannot be directly edited by the user from the command line, there is nothing to prevent the user from manually editing the source to "cheat" in games provided they know how to make the modification.

I am pretty sure the ▶ symbol was implemented to help the TI folks transition to the HP Prime. The := syntax was implemented (again I am guessing) so that it would be easy to program on a PC and transfer to the calculator. So if you program on the calculator, either is fine. They even use the same keystrokes (if you have alpha locked for the := notation). On a PC, it would be very impractical to use ▶ unless you have a special setup.

Source is now available at http://www.hpmuseum.org/forum/thread-95-post-2243.html#pid2243

You may be able to improve the speed by a large amount by switching to MAKELIST or MAKEMAT commands rather than appending elements to an existing list, etc.

Here are some screenshots to an upcoming update of the 3D grapher. More info here:

http://www.hpmuseum.org/forum/thread-95-post-1700.html#pid1700

export VSCROLL()
begin
  local i;
  dimgrob_p(G1,320,240);
  blit_p(G1,G0);
  for i from 239 downto 0 step 1 do
    blit_p(G0,0,0,G1,0,240-i,320,240);
    blit_p(G0,0,i,G1,0,0,320,240-i);
  end;
end;

This scrolls the current screen pretty fast. Modifying it for horizontal scrolling is also pretty fast.

export HSCROLL()
begin
  local i;
  dimgrob_p(G1,320,240);
  blit_p(G1,G0);
  for i from 319 downto 0 step 1 do
    blit_p(G0,0,0,G1,320-i,0,320,240);
    blit_p(G0,i,0,G1,0,0,320-i,240);
  end;
end;