<div dir="ltr"><div>Hi,</div><div><br></div>Originally project sounds as threaded object update for dependency graph, but seems it was extended.<div><br></div><div>= This week =<br clear="all"><div><br></div><div>From the code side only one thing is done: removed static and global variables from meta balls and curves code, essential for all ways of dealing with threaded depsgraph.</div>
<div><br></div><div>And then run into lots of design limitations which weren't so much difficult to solve for current "feature set", but which was expected to solve in a way ultimate feature set is possible.</div>
<div><br></div><div>This ended up in lots of discussions in IRC which just made me being completely unsure what actually to do.</div><div><br></div><div>Here's a wiki page with current proposal coming from Ton with cons/pros and possible ways to solve cons: <a href="http://wiki.blender.org/index.php/User:Nazg-gul/GSoC-2013#Thoughts_About_Design">http://wiki.blender.org/index.php/User:Nazg-gul/GSoC-2013#Thoughts_About_Design</a></div>
<div><br></div><div>Still not sure "copy everything" is a nice idea, needs more tech specifics aspect of this approach, not limit to generalish discussions how easy it is.</div><div><br></div><div>= Next week =</div>
<div><br></div><div>There're some things appeared in the design discussions which would be nice to implement anyway (which is locked rendering and threaded modifier stack).</div><div><br></div><div>And hope we'll finally find an ultimate way to go, which wouldn't smell like a deadeand from any of aspects.</div>
<div><br></div><div>= Questions =</div><div><br></div><div>Basically, only one question: which way to go.</div><div><br></div><div>Report is getting too long at this point, so wrapping around now.</div><div><br></div>-- <br>
<div><span style="color:rgb(102,102,102)">With best regards, Sergey Sharybin</span></div>
</div></div>