Jumpcore additional docs

FILES IN JUMPCORE, NOT COUNTING LIBRARIES:

Files you should edit:

Jumpcore “support” files:

FUNCTIONS IN JUMPCORE, NOT COUNTING LIBRARIES:

Works exactly like printf. When compiling in Debug mode, this prints the message given to STDERR. When compiling in Release mode, this does nothing.

Works exactly like printf. Prints the message given to STDERR regardless of mode. This is of dubious utility (on Windows/mingw, the message will be printed to a file named “stderr.txt”; on the Mac, it will be printed to the Console application, which few people know how to use or find) but the basic Jumpcore code uses it to report fatal errors which occur before the display surface is created.

A function that in a cross-platform way produces the absolute path to an “internal file”– On Windows, this means a file in the directory named “Internal” that accompanies the .exe. On the mac, this means a file in the “Resources” folder inside the application package.

An example method which draws the string “text” at screen coordinates x, y (Where the top of the screen is 1.0, and the bottom of the screen is -1.0), with rotation “rot” degrees, and optionally centered on the X and Y axes. Uses the global “uiFont” font.

A maybe-overcomplicated function for displaying a fatal error (given as “why”). All event handling will halt and a window will go up explaining the error; on the next keypress after this, the program will quit. Uses the global “uiFont” font (but is not dependent on drawText()).

Calls BombBox with a message stating “filename” could not be found.

FUNCTIONS IN JUMPCORE, NOT COUNTING LIBRARIES (”FULL VERSION” ONLY)

Self-explanatory color conversion routines.

Given the current-this-moment projection matrices, returns the pixel on the screen corresponding to the point (x, y, z) in 3-space.