Hi Richard, On Thu, Mar 25, 2010 at 7:57 AM, Schmidt, Richard <[email protected]> wrote: > Hi Robert, > yep, i think the easiest solution would be to have a proxynode with just one > filename. > > For the 'future' I would prefer an association (just the index of the > filename in the group) between the database query and the node which gets > paged in. So the database pager can 'mark' the query as loaded. This would > allow additional features like: > * Let the ProxyNode decide if it continues to query if the node isn't > loadable. > * Mark a node as dirty, so that the database pager will replace it with a > freshly loaded node. > > The 'null' children problem may be solved by having dummy nodes which are > still marked as dirty.
Having dummy nodes sounds a bit hacky. Design and implementation wise I'm more comfortable with having a single file to load per ProxyNode, then it'll simplify the interface and make it more straight forward to introduce extra variables and behaviours without introducing new concepts like dummy nodes. In hindsight I wish I'd caught this aspect of ProxyNode earlier when it was first submitted, and directed it towards having one filename per ProxyNode rather than present one filename per child. I'll have a ponder today on the topic of ProxyNode. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
