Hi, 2008/7/28 Øyvind Kolås <pippin@xxxxxxxx>: > The situation would be the same for GEGL once the bug in > http://bugzilla.gnome.org/show_bug.cgi?id=502465 gets resolved. Since > the part of the processing graph underneath the top most added stroke > doesn't change, and it can be recomputed from the parameters of the > nodes in the graph there is no need to always persist the actual > pixels. This is a general optimization that also will help other parts > of GEGL. Experimenting with the gegl-paint example in the GEGL sources > will be a natural thing to do when fixing this bug. (The code in there > should be easily modifiable to become full non-destructive again). Thank you for your comment. I don't how to recompute the destructive brush stroke yet. Or I might misunderstanding the meaning of "destructive." I thought destructive means "destroy image itself and cannot undo it nor redo it" unless we manage the undo cache. So it can't be non-destructive unless we save that cache forever. But maybe it's better to check the source code of gegl-paint first. -- Souichi TAKASHIGE _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
