Hi Aron,
On Fri, 2006-03-03 at 09:37 -0600, Aron Bierbaum wrote:
> I think that my
> >>> problem is that since both my structure change and my node
> >>> destruction happen in one sync call. The following would happen on
> >>> the server side:
> >>>
> >>> destroy Light1
> >>> change Light1
> >>> change Root
> >>> change Scene
> >>>
> >>> Changing the scene would then cause Node::invalidateVolume() to get
> >>> called on Scene node. While calling up the scene graph I get a
> >>> FieldContainerId similar to 161249600, which is definitely invalid.
> >>> My question is then, is there any reason that destroys get sent
> >>> before changes in RemoteAspect? Also I noticed that you are doing
> >>> change compression, could you also eliminate all changes for
> >>> FieldContainers that are being removed?
I'm not sure if that would work, as some of the consequences of the
changes might get lost.
But what I think might be a solution would be to change the order of
operations. If the RemoteAspect sent the destroys at the end of the
list, destroyed objects would be available until all changes have been
processed.
Marcus, Gerrit, any reason why that wouldn't work?
Dirk
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
