mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-01-13 00:04:19 +00:00
3768349a05
Previously, it wasn't safe to access Font instances from multiple
threads because there was a chance that they might reference the same
shared internal state. In this case, calling getTypeface() or getAscent from
two threads simultaneously would cause a race on the typeface and ascent
data members, even though the Font instances appeared to be disjoint.
With this change in place, it is now safe to use Font instances from
multiple threads simultaneously.
It is still an error to modify the same Font instance from multiple
threads without synchronization!
// Fine:
Font a;
Font b = a;
auto futureA = std::async (std::launch::async, [&a] { /* do something with a */ });
auto futureB = std::async (std::launch::async, [&b] { /* do something with b */ });
// Bad idea:
Font f;
auto futureA = std::async (std::launch::async, [&f] { /* do something with f */ });
auto futureB = std::async (std::launch::async, [&f] { /* do something with f */ });
|
||
|---|---|---|
| .. | ||
| juce_GraphicsContext.cpp | ||
| juce_GraphicsContext.h | ||
| juce_LowLevelGraphicsContext.h | ||
| juce_LowLevelGraphicsPostScriptRenderer.cpp | ||
| juce_LowLevelGraphicsPostScriptRenderer.h | ||
| juce_LowLevelGraphicsSoftwareRenderer.cpp | ||
| juce_LowLevelGraphicsSoftwareRenderer.h | ||