Hello,
[edit]don't use this attachment, use the one in my email below[/edit]

It's a font library, and it does funky stuff, hence why it's called funky font. Pointless showing a screenshot as it's the animation effect you need to see to appreciate it.

You can do the following with it:
1. display text with various alignments (left/right/centred/justified) and automatic wrapping.
2. add textures and various shading effects

but mainly the point of the library is
3. apply various effects

I use it in my latest game for example for contracting/constricting animated menus and displaying wrapped text in help.

the effects you can do are:
- 3d spinning/rotation effects
- text scattering
- various undulating effects
- shaking noise
- mexican waves
- heart beats
- etc.

Basically, you load a bitmap font then set some text, then you apply various effects to it, namely, spread/bouncing/sine/noise/rotate/scale/bow/damping.

Most things are done by calling one or two functions per logic frame and a replace textout function.

I didn't write it, btw, a friend did who's too shy to post (Graham). I'm just using it

source code plus a windows exe attached. just press letters a-z for some things you can do. and maybe 1-4 and 5-8 for other stuff.

Please note I wrote this AGES ago, which is why the code is completely vile. Obviously I'd do it differently these days.

Although that isn't an invitation for all you STL bandwagon sods to jump in.

No matter goring, I think it's superb now I'm using it.

Wow, some neat stuff in there. Is this in the depot? (lazy-ness prevents me from reading or searching)

I don't know, but it's attached to Neil's first post.

I can put it in the depot if anyone thinks it's worth keeping.

[edit]
If anyone gets it you'll need to change the code that uses function style casts for 'unsigned long' and 'unsigned short' to be explicit casts, i.e.

colour=unsigned long (blah)

should be changed to
colour=(unsigned long)(blah)

Doesn't come even close to compiling.

Of course it does, how do you think I attached the exe and I'm using it in my game

I've got it compiled via mingw and msvc, which near enough covers all bases.

Attached to this email is a new version fixing the cast bug with mingw and project files for devcpp and msvc8, the exe is from mingw.

I'll have a look, what version of gcc, I'm running 3.4.2 and that compiles fine. All those warnings are just float to ints mainly.

Are you running the version in my previous attachment, at line 109 it should read:
colour = (unsigned long) (m_source[x+mask_source_x]);

the error in your log points to the previous error which had it erroneously as
colour = unsigned long (m_source[x+mask_source_x]);

Oooh, the latest version compiles!

read my previous message

do you like?

Tis funky!

It makes me feel the old schoold days :p

I remember this funking thing from a few years ago.

Nice effects! I will certainly implement paragraph formatting with different adjustments in future Glyph Keeper. For the other effects, are there any examples of real games (or other programs) using them in meaningful way?

that was probably me too, it's taken me this long to start using it

I'm just using a few simple effects, one to show the currently selected menu item (contract/expand), another to show messages floating on the screen then as they scatter all over change the text then let it dampen back to normal to show the next message.

Most games use some kind of font transition effect. Just look at mario kart, there's messages that display with a sine wave effect, messages that have text pivoting/swinging, etc.

This is very cool. I liked the effect that was mapped onto key V.

Anyway, im definitely going to use this, even though its in c++. Although i do not understand that. Although it doesnt compile under C, i can't see where you / he uses any special c++ stuff. It'd be funny if the only c++ thing was bool.

It's only C++ in terms of the declaration of variables as and when I need them rather than at the top of functions, so it's nothing you can't turn into regular C easily enough.

Would:
#define bool unsigned char
work for porting to C?

It's better to define it this way:
enum bool {false, true};

yes it was very easy to "port".

The code was pretty neat and clean as well. It was easier to go through this than most of my old projects.

Anyway, in funkyfont.cpp, on lines #1647 and #1670, there is if (influence > 0.8) int john = 0;.

What was that going to be? It's like if(false) call_function(); especially seeing as how they are the only places in the whole file where there is a variable called john.

Is that the remnants of some old code, or some half-implemented stuff? I wasn't sure so i just commented it out.

Anyway, I've attached the modified files for anyone's convenience. I tested it and everything seems good.

[EDIT] This is GNU C / C99. I didnt re-order variable declarations becuase i cannot think of a c compiler that anyone uses that needs that. And im a very lazy person.8-)

It's because I'm a bad person. Basically when I want to stop a function without having a horrible assert box pop up I test for the condition, and inside the brackets I create a variable and stick a breakpoint on that line. And then I forget that I've done it and as a result my code is littered with "int a=0;" lines.

Turning that question around (and hijacking the thread at the same time), I've used a few libraries that define pragmas that stop the compiler if you compile it as c++ rather than c. What kind of things can you have in a C file that would stop it compiling as c++ ?

[edit]void pointers for one