Re: [info-performer] How to handle forked ISECT info ?

Date view Thread view Subject view Author view

From: Jean-Christophe Lombardo (jean-christophe.lombardo++at++cstb.fr)
Date: 12/01/2005 08:00:39

I've tryed this and it works well to pass data from APP to ISECT.
But the array of results is empty when seen from the APP process (in
PostDraw) although it has been filled in ISECT...

Donald Tidrow wrote:

>When you create the forked isect process, are you also creating an
>isectData region? That seems to be the main way of providing
>communications between the app and isect processes. You could set up a
>large chunk of memory and decide that the first 10k (for example) is for
>an array of segments to be tested by the isect process, and the next 10k
>is for an array of results that the isect process fills in. You
>probably would also need a couple of sync flags (also in the isectData
>memory) to let the app signal the isect process that new segments are
>ready, and a flag for the isect process to signal that the results are
>ready.
>
>Don
>
>
> 

-- 
Jean-Christophe Lombardo  - Salle Immersive "Le Corbusier"
http://salle-immersive.cstb.fr
EVE / Centre Scientifique et Technique du Batiment
290 route des Lucioles - BP 209 - 06904 Sophia Antipolis - France

Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Dec 01 2005 - 07:58:33 PST