- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Remove pattern from ENTITY
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-18-2009 08:52 AM - last edited on 12-18-2009 08:53 AM
I need to get rid of pattern from body for some reasons. Now I use method
ENTITY::remove_pattern() to do that, but in R18 help this method is signed
as Deprecated. And in R20 on-line help there is no information about this
method at all, it seems, but I can call it.
Tell me please, can I still use method ENTITY::remove_pattern() of R20 or
another solution of this problem is exists?
Re: Remove pattern from ENTITY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-18-2009 10:27 AM
Hello Igorunius,
The ENTITY::remove_pattern() method will remove pattern information from an entity (if it has any) and from all entities that are associated with the same pattern. This means that the entities will no longer have access to the pattern object and will no longer know who their "sibling" entities are. Note that you must call this method on one of the patterned entities. For example, if you call this on a body that contains patterned faces, nothing will happen - you must call it on one of the patterned faces or on a patterned child entity such as a loop, because the body itself isn't patterned.
It will not undo the pattern operation, however, in case that's what you really want to do. That is, all entities created by applying the pattern to the seed entity will still remain. To undo a pattern operation, as with any operation, you would use the history and roll mechanisms within ACIS.
By the way, we marked ENTITY::remove_pattern() as deprecated (although we kept the method public) because we wanted to discourage its use. ACIS uses pattern information internally to enhance performance (for example, during faceting), and we didn't want customers to experience performance degradation through the use of this method.
I hope this clarifies things. Please let me know if you need any further information.
Regards,
John

