Re: glUseFXFont problem

On Wed, 8 Jun 2022 07:29:11 -0400
Arden Llewellyn <[email protected]> wrote:

>Jeroen,
>
>So I modified my code and got it working again. It seems something changed
>when I took the update for RHEL 8.6. I had to use a fakeGetMaxChar to
>replace where I had font->getMaxChar() which was returning  1,114,111. That
>seemed too big so I tried an arbitrarily small number until my code worked.
>First I tried 65536 which worked, then went to 512 for no real reason...
>
>    const uint32_t fakeGetMaxChar = 512;
>
>Completely guessing, but part of the RHEL update included libreoffice fonts
>which "probably" is where my font was coming from. Not sure what happened,
>but, pure speculation on my part.
>
>Upgrade  libreoffice-opensymbol-fonts-1:6.4.7.2-10.el8.noarch
>Upgraded libreoffice-opensymbol-fonts-1:6.4.7.2-5.el8.noarch
>
>Would love to know if you have any ideas on why this might happen, the call
>to glUseFXFont would take 6-8 minutes to come back, but it would come back
>and the code would work after that. Anyhow, thanks for your great work on
>FOX, are you still maintaining it?
>
>thanks,

I had not run into that myself but it makes sense.  In the absence of
other information, I have pegged the range of characters to be the
full unicode set.

What the actual value should be is up for debate.  Not all fonts have
glyphs for all characters.

If turning a font into bitmaps, or better yet, a texture map, then you'd
want to render absent glyphs as a transparent rectangle, or a "replacement
glyph" of some kind.


		-- JVZ




-- 
+----------------------------------------------------------------------------+
| Copyright (C) 18:10 06/ 8/2022 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+