Re: Optimization ideas (was Re: 64 bit version of Quesa)

[James W. <ja...@fr...>]

I was looking at the view state stack, and wondered if we really need 
the attributeSet member of TQ3ViewStackItem.  It causes a 
Q3Object_Duplicate call every time we push the stack, and it looks like 
it's only there to support Q3View_GetAttributeState and 
Q3View_GetAttributeSetState.  Internally, we only call 
Q3View_GetAttributeSetState when writing view hints, and never call 
Q3View_GetAttributeState.  So I would think that whenever 
Q3View_GetAttributeState or Q3View_GetAttributeSetState is called, we 
could just build an attribute set on the fly from the various attribute 
members of TQ3ViewStackItem.  Anyone see a problem with that?
-- 
   James W. Walker, Innoventive Software LLC
   <http://www.frameforge3d.com/>