[info-performer] Deleting engines and engine sources/destinations?

Date view Thread view Subject view Author view

From: Hugh Fisher (hugh.fisher++at++anu.edu.au)
Date: 10/02/2004 23:24:30


 I've got problems with deleting pfEngines at runtime and
 am hoping someone can clarify a few things.

 The system is Performer 3.0.1 on Linux.

 I'm creating a number of engines at runtime that evaluate
 each frame, with either pfGetFrameTimeFlux() or my own
 pfFlux with floating point values as the only source. The
 destination is either an FCS or another pfFlux with one
 floating point value. The engines all have a user function
 to evaluate.

 The problem is deleting them. Engines that update an FCS
 in scene are no problem, they always clean themselves up
 when the scene graph branch they belong to is deleted.
 When I try to delete engines that have a source or dest
 but are not used in the scene (from the APP process), I
 get a segfault. And I do need to delete them, because the
 scene can be recreated quite often and if I don't there
 will be an ever-increasing number of them chugging away.

 Is there a particular order in which engines/fluxes
 should be deleted, or from a particular process? And is
 there a way to detach a flux from an engine, or an engine
 from a flux? The doco and header files explain how to
 add source and destination fluxes to an engine, but not
 how to remove them.

        Hugh Fisher
        DCS, ANU


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Oct 02 2004 - 23:35:13 PDT