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

[Tim Tautges]

Some cubit people are on this list already, but I also nominate Bob Kerr (cc'd) for this question.

- tim

On 08/19/2014 11:11 AM, shriwise wrote:
> Who is our contact for Cubit? Should I ask them directly?
>
> (Sending this a head of time so I don't forget. Paul might have a good idea on this...)
>
> Patrick
> On 08/19/2014 10:57 AM, Tim Tautges wrote:
>> Maybe so.  Would help to get a word from cubit people on this...
>>
>> - tim
>>
>> On 08/19/2014 09:56 AM, shriwise wrote:
>>> 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
>>>>>
>>>>
>>>
>>
>

-- 
Timothy J. Tautges
Manager, Directed Meshing, CD-adapco
Phone: 608-354-1459
timothy.tautges at cd-adapco.com