MultiProcessing and Intersections

New Message Reply Date view Thread view Subject view Author view

Curtis L. Goodhart (goodhart++at++cod.nosc.mil)
Thu, 11 Aug 94 09:09:23 PDT

On page of 177 of the User's Guide Table 7-4 syas that pfSegsIsectNode
should only be called from an ISECT or APP process. I dynamically
determine an object to highlight using pfChanPick (which I believe calls
pfSegsIsectNode). I do this from from a cull callback function. I guess
that's why it chokes and dies (from a child dying) ie because I am
calling intersections in a CULL process and I am multiprocessing.

When I put the pfChanPick in the application section it doesn't die but
the highlighting gets flaky and seems to jump from object to object
rather than stay on the object that I expect to be highlighted. Sometimes
objects that are ont supposed to be selectable for highlighting get
highlighted.

1) When and where does the ISECT process occur especially in terms
   of multiprocessing and the APP/CULL/DRAW model.

2) Any ideas on why the dynamically selected object seems to get flaky?

3) Does putting this call in the APP process seem the correct thing to do?
   Are there other choices that would make more sense? We don't want it in
   the draw process because it is the big time user already.

Thanks,

    Curt Goodhart

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:26 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.