Re: [K3d-development] Painter Cache [was:] Generic Polyhedron Primitives
Brought to you by:
barche
From: Bart J. <bar...@li...> - 2009-06-07 17:52:54
|
On Sun, Jun 7, 2009 at 4:56 PM, Timothy M. Shead<ts...@k-...> wrote: > Agreed, but on some level this approach doesn't really change the > underlying problem, it just means that we're using the node as the key > because it's stable, instead of something more appropriate. I'd like to > explore figuring-out what the "something more appropriate" might be > before falling-back on this approach. No! I didn't make myself clear enough: they part about keys remains unchanged from what is on the wiki page, i.e. array pointers or primitive pointers. The change is simply the removal of mesh_changed, and having the cached data connect to the mesh's changed signal directly. All cache initialization and reading now happens in the paint_mesh/select_mesh methods, which is the point where the pipeline is executed and all data is known. As an added benefit, all hint passing now happens through the standard hint mapping system, with no more need for the mesh_changed method. What is left to decide is: "How do we pass the change signal to the cached data?". Using imesh_source as argument for paint/select_mesh is one possibility, retaining the mesh argument but adding the change signal as extra argument is another. Cheers, -- Bart |