RE: [Plib-users] Compiling for windows

[Norman V. <nh...@ca...>]

Steve Baker writes:
>
>Norman Vine wrote:
>
>> Also FWIW there is some 'ugly' code in the FlightGear
>> Source cockpit / hud.hxx
>> that I used to speed up PLib text when I 'KNEW'
>> that I was rendering a lot of text with no intervening
>> glstate changes.
>> 
>> class fgText
>> class fgTextList
>> 
>> This code could probably be cleaned up a little bit
>> but it served its purpose for me as is :-)
>
>I don't know that code - but I thought about this very
>carefully when I wrote the FNT library.
>
>You *should* be able to avoid state costs when rendering
>text by using the begin()/end() member functions to
>bracket your rendering.  Did you need something beyond
>that?  I'd be suprised.

I worded that wrong  

I should have said 

There are a couple of utility classes in FlightGear
that demonstrate a method of collecting all of your
Text and Line primitives into 'displaylist' like structures
for 'all at once' rendering.

I found these useful so that I did not kill the frame rate 
with unnecessary state changes when drawing things 
like multiple HUD instruments that intersperse textured 
text and other graphic primitives

Norman