freetype-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Git][freetype/freetype-demos][master] [ftbench] Use proper `face_reques


From: Alexei Podtelezhnikov (@apodtele)
Subject: [Git][freetype/freetype-demos][master] [ftbench] Use proper `face_requester`.
Date: Fri, 12 May 2023 13:43:31 +0000

Alexei Podtelezhnikov pushed to branch master at FreeType / FreeType Demo Programs

Commits:

  • fb6dd3ee
    by Alexei Podtelezhnikov at 2023-05-12T13:43:29+00:00
    [ftbench] Use proper `face_requester`.
    
    It is wrong to forfeit the face ownership to the cache manager. Fixes #29.
    
    * src/ftbench.c (face_requester): Call `get face`.
    (main): Never pass `face` to the cache manager.
    

1 changed file:

Changes:

  • src/ftbench.c
    ... ... @@ -172,7 +172,7 @@
    172 172
     
    
    173 173
     
    
    174 174
       /*
    
    175
    -   * Dummy face requester (the face object is already loaded)
    
    175
    +   * Face requester for cache testing
    
    176 176
        */
    
    177 177
     
    
    178 178
       static FT_Error
    
    ... ... @@ -183,10 +183,9 @@
    183 183
       {
    
    184 184
         FT_UNUSED( face_id );
    
    185 185
         FT_UNUSED( library );
    
    186
    +    FT_UNUSED( request_data );
    
    186 187
     
    
    187
    -    *aface = (FT_Face)request_data;
    
    188
    -
    
    189
    -    return FT_Err_Ok;
    
    188
    +    return get_face( aface );
    
    190 189
       }
    
    191 190
     
    
    192 191
     
    
    ... ... @@ -1365,7 +1364,7 @@
    1365 1364
                          0,
    
    1366 1365
                          max_bytes,
    
    1367 1366
                          face_requester,
    
    1368
    -                     face,
    
    1367
    +                     NULL,
    
    1369 1368
                          &cache_man );
    
    1370 1369
     
    
    1371 1370
         font_type.face_id = (FTC_FaceID)1;
    


  • reply via email to

    [Prev in Thread] Current Thread [Next in Thread]