Gerrit Voss wrote: > Hi, > > On Thu, 2007-10-04 at 13:40 +0200, Marcus Lindblom wrote: >> Gerrit Voss wrote: >>> Hi, >>> >>> On Thu, 2007-10-04 at 13:23 +0200, Marcus Lindblom wrote: >>>> Carsten Neumann wrote: >>>>> Hi, >>>> And, for containers of pointers, we have a special class in our >>>> application that inherits std::vector<OurRefPtr<T>> and augmented it a >>>> bit with boost::indirect_iterator so that one can iterate either over >>>> objects directly (default), or over pointers (defined as ptr_iterator >>>> with ptr_begin(), ptr_end() and ptr_range()). It works well. >>> short question, do you handle something like automated parent >>> linking with this ? >> Nope. We don't need that currently. >> >> Is that why you need custom access/mutate functions? > > Yep, that's the interesting bit. Something like addChild does both, > the parent->child and the child->parent link.
Right. > The good thing is, currently there aren't that many cases where > this kind of auto linking takes place (mainly Node, Texture, > Properties). So the best way might be to compromise and only introduce a > class interface for the cases that do this kind of linking. Yup. It's probably a bit too tricky to build a wrapper for all MF ops that takes a parent & a MF and does the right thing. (Even if it would be kool, it smells overkill. :) Cheer, /Marcus ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
