[cgma-dev] copying iGeom entities in occ...

shriwise shriwise at wisc.edu
Tue Aug 19 09:56:38 CDT 2014


Agreed, but the function seems to be set up for this scenario as its 
only behaviour without consideration for a pure copy operation.

Patrick

On 08/15/2014 05:23 PM, Tim Tautges wrote:
> One case I can think of where this happens is in preparation for 
> certain boolean operations (e.g. subtract with option to keep the 
> original), you don't want the attributes on the body being subtracted 
> from the other.
>
> - tim
>
> On 08/06/2014 02:10 PM, Paul Wilson wrote:
>> Hi Patrick,
>>
>> On 08/06/2014 09:08 AM, Patrick Shriwise wrote:
>>> As for the topic at hand, my naive opinion is that attributes on the 
>>> original should never be removed and transferring
>>> these attributes should be optional in both cases. I can't think of 
>>> a scenario in which you would expect data do be
>>> deleted from the original upon copying it. It sounds like this may 
>>> be the case, but its buried pretty deep? Is that
>>> right, Paul?
>> I agree.  There must be something more complex happening that we 
>> don't see/understand.  It seems strange to ever delete
>> the attributes from the original entity when making a copy.
>>
>> Paul
>>
>

-- 
Patrick C. Shriwise
Research Assistant
University of Wisconsin - Madison
Engineering Research Building - Rm. 428
1500 Engineering Drive
Madison, WI 53706
(608) 446-8173



More information about the cgma-dev mailing list