<br><br><div class="gmail_quote">On Sat, Sep 25, 2010 at 9:31 AM, Cyrille Berger <span dir="ltr"><<a href="mailto:cberger@cberger.net">cberger@cberger.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="font-family: 'DejaVu Sans Mono'; font-size: 9pt; font-weight: 400; font-style: normal;">
<p style="margin: 0px; text-indent: 0px;">There is an other issue with systemLocked, it locks the entire layer, even if some area are now free for more processing. With a clever queue, it would be possible to know on which area an action needs to process. For instance, if we have a filter on the whole image and freehand stroke on a subpart of the image, as soon as the filter is finished with the subpart of the image, it will be possible to execute the freehand action, while the filter works on other area (and with a clever scheduler, you can give priority to that subpart).</p>
</div></blockquote><div><br>This is not possible with current Krita architecture. The transaction is created for entire paint device, not a part of it. Actually i don't know how to gather undo information when there are several simultaneous transactions possible on the same device.<br>
<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="font-family: 'DejaVu Sans Mono'; font-size: 9pt; font-weight: 400; font-style: normal;">
<p style="margin: 0px; text-indent: 0px;"></p>
<p style="margin: 0px; text-indent: 0px;">Second point, actions queue is the best solution for collaborative editing, since it would make collaborative editing as easy as adding an action on the queue of the node as soon as it is received.</p>
</div></blockquote><div><br>Yep, and mipmapping can be implemented on the top of it as well.<br><br> </div></div><br>-- <br>Dmitry Kazakov<br>