> 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.
Yes, please. An interactive typewriter mode is an interesting idea for `ftstring` only. I wonder if you could implement it for any keyboard including non-Latin. This might require some modification of the graph/ library. Can you look into it? Thanks, Alexei
