Hello Johannes,
On 11/22/2011 03:27 AM, Johannes S. Mueller-Roemer wrote:
> to ensure the correct ordering of rendering stages (e.g. SimpleStage), I
> have been attaching the stages that need to be executed first as
> children of the stages that need to be executed later on.
hmm, I'd just make them children of one node in the order the stages
need to run.
> This works for
> SimpleStages so far, but now I require the same with an AlgorithmStage,
> but when attaching a SimpleStage to an AlgorithmStage, the child is not
> visited. Is there any way to ensure the children of an AlgorithmStage
> are visited, or another way to ensure execution order is maintained? A
> simple example is attached.
yes, that is by design, it is the algorithms responsibility to traverse
the scene below the stage (this allows for example multi pass algorithms).
That probably requires the algorithm to be implemented as a
FieldContainer that has the StageHandlerMixin as a parent. See e.g.
Source/System/Dynamics/Skeleton/OSGSkeletonParent.h for an example how
to get the mixin into the inheritance hierarchy.
From the algorithms execute() you'd then just call
this->recurseFromThis(action).
Cheers,
Carsten
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
