RE: [Freetype] Windows code displaying garbage - any help?

[Pedriana, Paul]

You would probably be done with this problem by now if you simply did
what the original suggestion was and run your code and put a breakpoint
after the Freetype glyph loading code and looked at the data in your
debugger. If this is too hard for you then perhaps you are in over your
head and should come back to Freetype when you get a little more
programming experience. 





-----Original Message-----
From: Jason C. Weaver [mailto:address@hidden 
Sent: Monday, June 02, 2003 3:13 PM
To: address@hidden
Subject: Re: [Freetype] Windows code displaying garbage - any help?

I can certainly go through that exercise but it just seems that the
process of converting a FreeType bitmap to a Windows bitmap would be
well documented somewhere.  Either that or that someone would have
provided a simple example by now.  If someone has documented this or
there is a simple example I would surely appreciate someone letting me
know where it is.  It would save me a great deal of time and halt the
continued frustration with this integration effort.

Thanks for any more information.
Chris





--- Greg Inman <address@hidden> wrote:
> To check the Freetype bitmap it might help to print it to standard 
> output. Then you can check it pixel by pixel.  For a pixel that is 
> background use 'O' and for a pixel that is set use 'X'.  At the end of

> the scan line start a new line.
> 
> You may be able then to see how your interpretation of the Freetype 
> bmp is flawed.
> 
> Greg






> ----- Original Message -----
> From: "Jason C. Weaver" <address@hidden>
> To: <address@hidden>
> Sent: Monday, June 02, 2003 2:55 PM
> Subject: Re: [Freetype] Windows code displaying garbage - any help?
> 
> 
> > Thanks for the suggestion.  I've already verified that my Windows 
> > code
> works (see my original
> > email)  ;)  It properly displays my hand-made bitmap at my hard-code
> (300,300) point.
> > Chris