Dear Jules, Roli Team and Community,
I have updated Juce library to the last commit and I observed there is a jassert done in the c786c commit.
Such (two) jassert are in juce_font.cpp:
void Font::getGlyphPositions (const String& text, Array& glyphs, Array& xOffsets) const
// This call isn’t thread-safe when there’s a message thread running
jassert (MessageManager::getInstanceWithoutCreating() == nullptr
At this point, it results that my code raise and exception in such assertion when before of that cited commit, it worked flawlessly (IMHO).
Here are the details:
- On one hand, of course I have a JUCE GUI (Working in Windows, OSX and Linuxes) with the appropiate MessageManager.
- On the other hand, I have several Graphics contexts not related to any GUI component (so not related with MessageManager). They are created and managed in/by a Job Pool for video ouputting in a Video Broadcast card.
So, when I want to use fonts in such JobPool/Image environments, the assertion jumps warning that the MessageManager is not locked. Do I need to to lock it? I have tried but I cannnot get the lock, alledgelly because there is no relation?
To sum up:
Do i need to lock the message manager?
Is it needed to refine such assertion in order to contemplate the use of a Graphic/Image context not related to any component and so, not related to the message manager (but there is one!)
Thank you in advance,