Robert,

I was just curious to see if anything was committed to the 2.9.x / 2.10 
baselines for this.  I know that you stated that you already had code in place 
to fix this issue.  Thanks.

Ryan H. Kawicki
The Boeing Company
Training Systems & Services
Software Engineer

-----Original Message-----
From: Kawicki, Ryan H 
Sent: Friday, July 24, 2009 10:44 AM
To: OpenSceneGraph Users
Subject: [osg-users] FW: Importance Of Node Path List In Database Pager


 
> Have you implemented a fix yet? If not I'll try to get to it while I'm still 
> around this week/early next week.

Unfortunately, we have not come up with a fix.  If you like, I could come up 
with a solution and submit it, but I would hate to duplicate work if you 
already have it on disk somewhere.  I will be out most of next week and would 
not be able to get to it until sometime the following week.

Thanks for the continue support.

Ryan H. Kawicki
The Boeing Company
Training Systems & Services
Software Engineer

-----Original Message-----
From: Robert Osfield [mailto:[email protected]]
Sent: Friday, July 24, 2009 9:20 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] Importance Of Node Path List In Database Pager

Hi Ryan,

On Fri, Jul 24, 2009 at 3:01 PM, Kawicki, Ryan H<[email protected]> 
wrote:
> Would it be possible to store this information as a DatabaseRequest attribute?

Curious, I thought I had already made such a change to DatabasePager - to move 
the NodePath acquisition  to the DatabaseRequest set up, but now reviewing it 
this code isn't in svn/trunk.  Weird.  Perhaps I thought about implementing it 
and then got distracted.... or perhaps I did the experiment but not checked it 
in.

Such a change would be appropriate - adding a RedNodePath to DatabaseRequest 
and set it inside the DatabasePager::requestNodeFile().  Unfortunately such a 
change would break the ABI for 2.8.x so would have to be merged with just the 
svn/trunk and the 2.9.x/2.10 series.

>The node path should be computed during the cull traversal.  The problem here 
>is that there is the possibility for a parent iterator to become invalidated 
>when this operation traverses up the scene graph.
>
> Sorry about the confusion on the line number.  I am referencing OSG 2.8.1.

Thanks, I now understand the issue at hand.  One I have previous thought about, 
but alas wrapped up this work...

Have you implemented a fix yet? If not I'll try to get to it while I'm still 
around this week/early next week.

Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to