[RELEASE] intraFont 0.22 - with S-JIS support

[BenHur]

intraFont 0.22 is out, it has a couple of fixes and optimizations and two new features:

1. S-JIS string parsing for developers using Japanese
2. ASCII characters caching (for those who need only the standard character set, but want to save on memory and loadtime)

More details in the readme.

Cheers, BenHur

[Coolj]

Great :D

[transce08]

That's hot.


For other devs, here are a couple functions that are handy if you want a simple method to write one string or integer at a time.

Edit: change the size of the array as needed.

Spoiler for custom intraFont functions:

//print text to screen using font 
void printFontScreen(int x, int y, char* display, intraFont* font){
	guStart();
	intraFontPrint(font, x, y, display);
	sceGuTexMode(GU_PSM_8888, 0, 0, 0);
	sceGuFinish();
	sceGuSync(0,0);
}//end printFont 

//print int to screen using font
void printFontScreen(int x, int y, int i, intraFont* font){
	guStart();
	char number[5];
	snprintf(number, sizeof(number), "%i", i);	
	intraFontPrint(font, x, y, number);
	sceGuTexMode(GU_PSM_8888, 0, 0, 0);
	sceGuFinish();
	sceGuSync(0,0);
}//end printFont

[Raphael]

char number[5];
snprintf(number, sizeof(number), "%i", i);

What if someone tries to print a number with more than 4 digits?
Apart from that, it's ugly graphics.c style (ab)usage of sceGuSync() which just wastes CPU cycles like hell.

[transce08]

Originally Posted by Raphael

What if someone tries to print a number with more than 4 digits?

Obviously, they change the size of the array. I thought the code was transparent enough that it didn't require explanation. And yes, it's inefficient for large amounts of text but it is beginner-friendly.


Edit: About the sceGuSync(), I couldn't remember why I had put it there at first but now I remember that without that line, you end up getting graphical errors and you get distorted characters showing up on random parts of the screen.

[Mr305]

Cool. Academika suite will rock with this...

[Art]

Hi,
It appears if you go over a certain size, the colour information is ignored.
is this a bug, or am I doing something wrong?

ie. This prints GREEN:

        intraFontSetStyle(ltn[8], 1.0f,GREEN,BLACK,0);
	intraFontPrint(ltn[8], 180, y, "Hello World!");

This prints the right text with the previously defined colours

        intraFontSetStyle(ltn[4], 1.0f,GREEN,BLACK,0);
	intraFontPrint(ltn[4], 180, y, "Hello World!");

Cheers, Art.

[Xsjado7]

this looks mad

[BenHur]

Originally Posted by Art

It appears if you go over a certain size, the colour information is ignored.
is this a bug, or am I doing something wrong?

The sample does excactly what it's supposed to.

Probably you don't understand the way intraFont works:
ltn[4] and ltn[8] are not different sizes of the same font, but two independent fonts: in the fonttest example ltn is only an array holding all 16 ltn*.pgf (latin) fonts (large/small, w/without serif, regular/italic/bold).
intraFontSetStyle sets the style of ONE font: the one you feed the the function (either ltn[4] or ltn[8])
intraFontPrint prints using the selected font (either ltn[4] or ltn[8])

my suggestion: study intraFont.h and the sample properly or forget about it until there's a noob-proof version of it (no offence).

Cheers, BenHur

[Art]

Fair enough, I'll wait for the noob friendly version.

Meanwhile, since I haven't seen any demo made with it,
It would be good to see the source if anyone does do a real time demo
with scrolltext, or anything dynamic like that.
Perhaps then it will be easier to see how it's handled.