Re: some freetype 2 questions (and a patch)

[David Turner]

Hi Toby,

> 
> also, would it be possible to make FT_Outline_Render ignore the bitmap.buffer
> member when rendering direct? I only use the bitmap to pass dummy size
> information, but I have to do the following:
> 
>   bmp.buffer=(unsigned char *)1;
>   //bmp.buffer=NULL;
> 
> In order to stop FT_Outline_Render() returning FT_Invalid_Outline(!).
> 
I've just commited a fix. Now, the target buffer won't be checked
in direct rendering mode.

Thanks for the report..

> Toby.
> 
> lastly, here's a patch for fterror.h. I use fterror.h in a rather nonstandard
> way to build a case statement that converts from ft error code to ft error
> string, and also to expose the ft errors to python.
> The extern "C" {} stuff gets in the way when I do this. I appreciate that
> there are cases where it's needed, but I think that for the non default
> case it should be the responsibility of the includer, rather than the include
> file itself. thus:
> 

Please check also the last "fterrors.h" from the CVS. It contains changes
that correspond to your patch..

Chers,

- David

> diff -w -B -u -r1.10 fterrors.h
> --- fterrors.h  2000/09/15 22:50:57     1.10
> +++ fterrors.h  2000/09/26 23:10:48
> @@ -44,10 +44,8 @@
>  #define FTERRORS_H
> 
> 
> -#ifdef __cplusplus
> -  extern "C" {
> -#endif
> 
> +#undef NEED_CLOSE_EXTERN__
> 
>  #ifndef FT_ERRORDEF
> 
> @@ -55,6 +53,11 @@
>  #define FT_ERROR_START_LIST     enum {
>  #define FT_ERROR_END_LIST       FT_Err_Max };
> 
> +
> +#ifdef __cplusplus
> +#define NEED_CLOSE_EXTERN__
> +  extern "C" {
> +#endif
>  #endif /* !FT_ERRORDEF */
> 
> 
> @@ -184,7 +187,7 @@
>  #undef FT_ERRORDEF
> 
> 
> -#ifdef __cplusplus
> +#ifdef NEED_CLOSE_EXTERN__
>    }
>  #endif