Recent changes to feature-requests

Correct bbox position of all text render.

Anonymous — Mon, 11 Mar 2013 19:04:15 -0000

Hello.
I want to render font to FBO buffer, and i need a correct width and height (pixel to pixel) of all symbols and all area that's rendering.

Till now i use this function.

void SizeForString( FTSimpleLayout *simpleLayout, LPWSTR str, int &width, int &height )
{
FTBBox size_ = simpleLayout->BBox( str );
width = (int) round( size_.upper.X() - size_.lower.X() );
height = (int) round( size_.upper.Y() - size_.lower.Y() );
}

I can compile the source version 2.1.3(have compiled year ago when was some problem with Z position).
What i must do, to get a correct coordinates?

Correct bbox position of all text render.

Anonymous — Mon, 11 Mar 2013 05:40:54 -0000

Hello.
I want to render font to FBO buffer, and i need a correct width and height (pixel to pixel) of all symbols and all area that's rendering.

Till now i use this function.

I can compile the source version 2.1.3(have compiled year ago when was some problem with Z position).
What i must do, to get a correct coordinates?

Newline parsing

AnotherUser — Sun, 21 Aug 2011 20:41:57 -0000

Hello, Thanks very much for ftgl, it does exactly what it says on the tin.

Of course, I have one request :). Would it be possible for font->Render to create a new line for newline chars? Currently inserting a newline char just creates a "box" substitute char instead.

This would of course also affect bbox computation too...

More options on fonts

Jacob F — Tue, 22 Mar 2011 21:58:28 -0000

I want to be able to render outline fonts without GL_LINE_SMOOTH enabled.

For texture and buffer fonts:
I want to be able to render them with GL_NEAREST interpolation.
I want to be able to have them not anti-aliased like bitmap fonts.

Make texture and buffer fonts not clipped at the edges

Jacob F — Tue, 22 Mar 2011 21:41:52 -0000

It would be nice if texture and buffer fonts would not clip at the edges.

Migrate to autoconf GL macros

Carlo Bramini — Tue, 25 Jan 2011 10:12:40 -0000

For improving portabilty, increasing the number of supported platforms and at the same time reducing greatly the amount for code written for the configure script, I suggest to abandon the functions written for detecting GL, GLU and GLUT in favor of the autoconf GL macros.
Here there are some references:
http://www.gnu.org/software/autoconf-archive/ax_check_gl.html
http://www.gnu.org/software/autoconf-archive/ax_check_glu.html
http://www.gnu.org/software/autoconf-archive/ax_check_glut.html
Using AX_CHECK_GL/GLU/GLUT macro has also the advantage to detect different implementations of openGL that typically provides different include files (like OpenGL/GL.h) and different libraries at linking (like -lopengl32 on Windows platforms).

Big overhead in FTTextureFontImpl::Render

Anonymous — Fri, 18 Jun 2010 04:53:14 -0000

FTTextureFontImpl::RenderI() does a bunch of calls to back up the current blend settings and enable textures everytime it is called. These turn out to be a huge bottle neck when drawing a lot of text at once, and only need to be done once.

In my tests, by removing these calls and ensuring the correct blending and texture modes are set before batch calling FTGL, drawing 20,000 text strings goes from 300ms to 100ms.

Perhaps FTGL could include a stream-lined version of FTTextureFont?

Allow FTGL to run on OpenGL 3.X only systems

Silverstein — Thu, 06 May 2010 18:49:32 -0000

I'm assuming that currently FTGL will not run on systems that have only OpenGL 3.X support. So this is a request to allow FTGL to run on systems that have only OpenGL 3 support (and which do not support the earlier OpenGL versions).

Add method to get FTGL version information

Paul Obermeier — Sun, 04 Apr 2010 17:47:26 -0000

It would be nice, if FTGL had a possibility to determine the library version at runtime.
This could be done either with a function call (like OpenGL's glGetString) or by defining some macros (#define FTGL_MAJOR_VERSION 2, ...).

Thanks,

Paul

FTSimpleLayout advance raster pos

Anonymous — Fri, 19 Sep 2008 09:14:38 -0000

I like the rendering with FTSimpleLayout, but what I miss is an option to change properties of my text, for example color, halfway the text. I think a solution would be to advance the raster-position, so that you can render some text, change a few options and then render some more text starting from where your last text ended.