Got it. Will do soon. :)
On Tue, Aug 6, 2019 at 6:28 PM Alexei Podtelezhnikov
wrote:
> >> In other words, 'ft_glyphslot_preset_bitmap' should be looping through
> >> appropriate renderers calling 'get_glyph_bbox'. This is how it is
> >> supposed to work.
>
> > Currently, in
>> In other words, 'ft_glyphslot_preset_bitmap' should be looping through
>> appropriate renderers calling 'get_glyph_bbox'. This is how it is
>> supposed to work.
> Currently, in `ft_glyphslot_preset_bitmap', after getting the cbox, some math
> is done on it and ultimately top-left and sizing
>
> In practical terms, we need the bounding box to initialize the
> top_left and the bitmap size. These values might be needed even if the
> actual memory allocation and rendering is postponed indefinitely. One
> should *not* expect immediate allocation of memory and rendering. For
> this purpose
>
> In practical terms, we need the bounding box to initialize the
> top_left and the bitmap size. These values might be needed even if the
> actual memory allocation and rendering is postponed indefinitely. One
> should *not* expect immediate allocation of memory and rendering. For
> this purpose
>
> So, I guess I should instead rely on the bounding box functions that the
> libraries provide now? Let me know your views.
>
In practical terms, we need the bounding box to initialize the
top_left and the bitmap size. These values might be needed even if the
actual memory allocation and
