On Fri, 31 May 2019 14:16:43 +0200, Mike Wey wrote:
It was "fixed" by only displaying the message when GTK is build with
debugging enabled:
So most likely the windows libraries are build with debugging enabled.
You're right. Thanks.
I updated to 3.24.8 which is apparently NOT compiled with debugging hooks and it went away.
But properly setting the
expandandfillparameters in the packStart
call would be the proper fix for this use case.
Yup. Got that working, too.
Now I'm just working on how to stop the "couldn't load font" errors. From what I've found so far, this may be a problem with the application not waiting long enough between loading one font and the next? I don't know. I thought that stuff would be asynchronous. I don't really care if the fonts don't load as long as it's not spitting out those errors.
So, I'm currently looking at how to conditionally load the fonts based on whatever reason it's failing... which so far has eluded me.