Re: [PATCH] add ability to change the rendered text while program is running

[Freetype Supporter]

On Tuesday, August 3rd, 2021 at 10:04 AM, Alexei Podtelezhnikov 
<apodtele@gmail.com> wrote:

> > In future just send to freetype-devel in to and you can CC me ( probably 
> > unnecessary because i am subscribed to mailing list)
>
> I did not Cc the list. I used To to both you and the list. You have to
>
> Reply All. It is just common etiquette.
>
Well i'm adding the list now. I will make sure future emails have 
freetype-devel in them.

> Anyway. I need a rationale why a screen full of ASCII characters is
>
> not enough for you (it is already available). Why do you need the
>
> interactive mode? It is not about harm, tt is about bloat. These tools
>
> have rather narrow user base among font developers and freetype
>
> testers. Why do we need it?
It could be useful because sometimes when you are testing, you like to get an 
idea of how the font works with different combinations of characters without 
having to keep reopening the app.

I forgot about bloat, it makes sense for ftview since all characters are 
already visible.

While all characters are visible in order in ftview, things like kerning need a 
specific sequence of characters in order to compare and verify.

You are 100% right that its a better fit for ftstring, i totally agree with 
you. I should reapply patch there.