From: Boris Mansencal (boris.mansencal++at++inria.fr)
Date: 02/15/2001 00:17:45
Angus Dorbie wrote:
>
> Looks like I was wrong the hit array is for multiple segments (as you
> suggest).
>
> Looks like you'd need to use callback to get access to all the segments.
I don't really understand your answer. Why would I need to use callback
?
With the current behavior, I can access to the 'closest' intersection of
each segment with the scene. But what I need is all the intersections
of
a given segment with the scene.
I thought that it was possible because we pass a pfHit **[] to isect,
but
it seems it is not.
So I don't understand why we do not pass only a pfHit *[] ?
Is it for a coming feature ?
Is the behavior that I expected present in the 2.4 release ?
If not, do you think to a clever way to do this ?
Thanks a lot,
Boris.
>
> Cheers,ANgus.
>
> Boris Mansencal wrote:
> >
> > Angus Dorbie wrote:
> > >
> > > Boris Mansencal wrote:
> > > >
> > > > Hi,
> > > >
> > > > I would like to get all the geometries intersected by a segment.
> > > > It is not possible with pfNode::isect(pfSegSet *segSet, pfHit **hits[],
> > > > isn't it ?
> > > >
> > >
> > > It is possible.
> > >
> > > > So, why do we need to give a pfHit **[] and not only a pfHit *[] if we
> > > > get only
> > > > one intersection point by segment ?
> > >
> > > Because it's possible :-)
> > >
> >
> > So, as isect returns n the number of intersections, I will have n pfHit*
> > from hits[0], right ?
> > Is it still working with several segments ? How do I know the number of
> > intersections for a given segment ?
-- Boris Mansencal INRIA Rocquencourt (France) - projet i3D
This archive was generated by hypermail 2b29 : Thu Feb 15 2001 - 00:17:53 PST