Re: Getting Node info from IsectNode

New Message Reply Date view Thread view Subject view Author view

david pratt (pratt++at++bessie.cs.nps.navy.mil)
Wed, 19 Jan 94 23:07:20 -0800

I had the same type of problem trying to blow up buildings. To get around
the performer 1.0 limitations on returning intersections, here is what I did:

When you read in the piece of database, put a intersection call back in.
  The call back stores the address of the node as it is being traversed. Make
  sure it is a global so you can get it.

At traversal time, when the node is traversed - the address will be stored.
When an intersection is detected, stop the traversal. At this time, the
address of the last traversed node will be stored and you can use that
for the display node.
   Dave

Dave Pratt pratt++at++cs.nps.navy.mil (408) 656-2865
Department of Computer Science, Naval Postgraduate School, Monterey, CA 93943
These are my opinions, talk to the PAO for the Navy's.

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:09 PDT

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