<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi,<br></div><div><br></div><div>I'm reading back <span>through the mailing list to gain some knowledge. I found this comment from Phil:</span><br></div><div><a href="https://lists.cuis.st/mailman/archives/cuis-dev/2021-August/003850.html">https://lists.cuis.st/mailman/archives/cuis-dev/2021-August/003850.html</a><br></div><blockquote type="cite"><pre>If that is the issue, I think there's a larger problem to be solved.
Morphic is inherently not thread safe so you're dealing with an intractable
problem (short of re-architecting Morphic.) Other than marking a morph
for redraw, anything else touching Morphic from a background process needs
to be wrapped in UISupervisor whenUIinSafeState: [].<br></pre></blockquote><div><br></div><div>What makes Morphic inherently not thread safe? Why the community didn't addressed this shortcoming when the Morphic framework was reachitected anyway?<br></div><div><br></div><div>Regards,<br></div><div>Szabolcs<br></div></body></html>