Mario Veraart (rioj7++at++fel.tno.nl)
Fri, 31 Oct 1997 16:01:45 +0100 (MET)
What I do is use shared memory to give the data back.
The function pfGetIsectData() returns a pointer to the copy of the
isect data that APP has. APP makes a copy of it and gives it to ISECT
when you call pfPassIsectData(), at the next call to pfFrame().
A new call to the isectfunction is made when pfPassIsectData() was
called.
My sceme is use shared memory to let the APP know that ISECT has done
the calculation and then set up new data in the IsectData and call
pfPassIsectData().
if (shared->isectReady) {
... process previous isect data
... setup new data for isect
shared->isectReady = FALSE;
pfPassIsectData();
}
My question about a forked ISECT process:
The isect function is called ones before the first call to pfFrame().
I have the impression it happens in the pfConfig() call.
Does anybody know if this is true.
Mario
=======================================================================
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:09 PDT