Tom Impelluso (verdi++at++piano.ucsd.edu)
Thu, 2 Oct 1997 13:15:34 -0700
I have an interface (using xforms) that sproc()'s a
Performer Code.
There are two buttons on my interface (amongst others).
1) Run Performer
2) Kill Performer
When I hit button -1-, the xform-app sprocs the performer code
(which, in turn, sprocs a finite element code). All is well.
When I hit button -2-, the xform-app changes a global variable
(which the performer process can access and test against).
The change causes the performer code to die (pfExit, and all that).
When I hit button -1- again, I received warnings:
pfDataPool::create arena /usr/temp yadda yadda yadda already exists, attaching instead
pfConfig() Cannot config more than once.
pfuInitInput() Input already initialized. Returning...
I assume the problem relates to the fact that since the sproc'd
performer code is in the same data space, that one config is enough.
Similiar for the others.
Now...
Is there a command I can issue before the pfExit() (or even after)
that can clean things up, allowing me to re-state the pfConfig,
pfuInitInput, and whatever command caused the belch regarding the arena
(By the way, tell me what command that was, if you know, please).
Thanks
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:03 PDT