Re: Sharing Geometries

New Message Reply Date view Thread view Subject view Author view

Prakash Mahesh (prakash++at++DRAWCOMP.COM)
Wed, 23 Dec 1998 15:29:09 -0500

This is from the man pages for pfgeostate:
        pfGeoSet::setGState increments the reference count of the new
pfGeoState
     by one and decrements the reference count of the previous
pfGeoState by
     one but does not delete the previous pfGeoState if its reference
count
     reaches zero. pfGeoSet::setGStateIndex does not affect pfGeoState
     reference counts.

     It is important to understand and remember that any pfGeoSet
without an
     associated pfGeoState will not be rendered with the global, default
state
     but will be drawn with the current state. To inherit the global
state, a
     pfGeoState which inherits all state elements should be attached to
the
     pfGeoSet. pfGeoSets should share like pfGeoStates for space and
rendering
     time savings. See the pfGeoState reference page for full details.

---


And here is how my nodes are :


	pfGeoState1	pfGeoState2
		\      /
		pfGeode
		   |
		pfGeoSet


If I don't do a geoset->setGState, is there a way to let pf know that I
want to use the attributes of pfGeoState1 while it renders the first
geoset and pfGeoState2 while it renders the same geoset again (say these
are translated using a pfDCS)? 


Is there a way to introduce the GeoState into the scenegraph somehow so
that the traverser knows to use the attributes that are "current".


Hope I am clear about my question.


Thanks for any help.







-- 
  Prakash Mahesh                                     
  prakash++at++drawcomp.com
  	--or--
  prakash++at++openworlds.com















New Message
Reply
Date view
Thread view
Subject view
Author view











This archive was generated by hypermail 2.0b2 
on Wed Dec 23 1998 - 12:39:40 PST





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