Re: Custom geometries

[Roger H. <rog...@mi...>]

I am currently defining kQ3XMethodTypeGeomCacheNew etc locally and am
almost happy with defining custom geometries but I have hit a snag.

E3XObjectHierarchy_NewObject calls E3ClassTree::CreateInstance  with the
middle parameter (sharedParams) equal to kQ3True. This means the 
parameter
gets passed all the way down, so when 
OpaqueTQ3Object::InitialiseInstanceData
is called for the geometry class, and it finds the 'newMethod' is null, 
it then calls
to Q3Memory_Copy which copies rubbish data over the cachedObject field 
(etc) of
E3Geometry. This later causes rendering to crash.

I think the safest way to fix this is to write a new method for the 
geometry class. As it
happens it does not need to do anything as the fields have been cleared 
already.

Any objections, or thoughts on a better way forward?

Roger Holmes.



On 23 Aug, 2005, at 14:39, Roger Holmes wrote:

>
> On 23 Aug, 2005, at 04:35, James W. Walker wrote:
>
> Yes I do, though the plan is to save files in the existing format so 
> any other applications
> (or old versions of our own applications) can still read the files. I 
> could use a custom
> group perhaps. Or I could just #include "Globals.h" and patch it up if 
> it changes later.
>
> I am not asking anyone else to do any work, but I would not want to 
> take Quesa in a
> direction which would upset anyone's plans.
>