Oh right, I see now.

Yeah, your program is looking very cool. This will be very useful, I can see that. So is this going to use a parse hook and font hook?

Only the parse hook.  Font hooks are too slow because they are used by the slow Ti-OS routines.  Instead, fonts will be compiled as programs, such as pgrmMYFONT.

Oh, well there is a neat twist!. So you are going to be making the routine for how Output( and the like act? That is really nice and that will make the routine fast as well.

Ah ok I see. Still it's an awesome project, though. It will really be useful for BASIC coders because using custom fonts in BASIC with xLIB/Celtic/DCS is slow.

Quote from: DJ Omnimaga on November 13, 2010, 03:22:45 am

* DJ Omnimaga wonders if this will be useable in Axe

Not unless we can incorporate it.  Sorry --but then since you can display sprites/tilemaps in axe, you really don't need it

Quote from: Xeda112358 on November 13, 2010, 03:24:36 am

Oh, well there is a neat twist!. So you are going to be making the routine for how Output( and the like act? That is really nice and that will make the routine fast as well.

Yes.  Output will display a custom standard 6x8 font, and Text() will display a custom sized font, the default being the size of small text.  The limitation is all characters must be the same size.

So just for clarification, both Output( and Text( draw to the graphscreen, right?

Sounds great! Good luck on this.

You mentioned this on the first page, but I wanted to be sure. Each font set can contain a total of 256 characters? Is there a reason for the limit? I will admit though, it seems very unlikely that anyone would need more that 256 characters.

Well, the TI-OS font has 256 chars, and it seems reasonable...

Since I know that you can have the font set archived, I just have one tip from experience. Store the location of the font set in the archive in ram, don't re-find it every time.

No sooner said than done!

But if a font is located in RAM, would deleting and adding variables change its location?

Each font set can contain a total of 256 characters? Is there a reason for the limit? I will admit though, it seems very unlikely that anyone would need more that 256 characters.

It's a reasonable standard.  But the reasons I'm doing it is there aren't very many tokens available on the Ti-83+.  Sure, there's more than 256, but here's what I have to keep in mind, for example:

1. For people who want to save space in their Ti-Basic program, they'll use tokens instead of lowercase letters in their strings to display.
2. For people who want easy-to-remember characters by using standard ASCII (and don't care about program size), they'll use lowercase letters instead of tokens pertaining to ASCII 97 to 122.

In both instances, the same font characters will be displayed.  But that means I need both sets of tokens available.  So there aren't much more than 256 total possiblitities for a character from a font.  However, with the option to have several fonts available for the same program, that won't make much of a difference.

As long as the font sets won't take space for 256 chars even when they contain 40 or so, I am fine.