Hello Michael,
Michael Raab wrote:
> thanks for your quick answer. What does compacting changelist exactly do?
all "changed" entries for a container a replaced by a single "changed"
entry that marks all fields as modified. "AddRef"/"SubRef" entries are
summed up, so that only AddRefs (if any) are left and if there is a
"destroyed" entry the container will not show up in the list at all.
> Do you think it would make sense to sync more often than just one time, e.g.
> after different sub trees where created?
only if the size of the CL is actually the problem or you are concerned
about performance. It may take a while to transmit a huge scene across
the network, but that is true whether you do it in one big chunk or
multiple smaller ones.
> What would be the best solution to execute such sync? Calling
> MultiDisplayWindow::render() or something else?
yes, probably. I don't think there are any interfaces that let you
trigger syncs explicitly.
Cheers,
Carsten
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
