If the parent block is just a container for inserting multiple objects and
is going to be exploded anyway, that's another matter and no, you didn't
make that clear earlier.
What puzzles me is the approach you cite to do it, because it makes no
sense. When you explode something, you can get the resulting objects very
easily, but perhaps Jerrry doesn't know how to do that.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010
http://www.acadxtabs.com
Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
wrote in message news:6288237@discussion.autodesk.com...
Tony,
It is confusing. However I had a nice long conversation with Jerry Winters
who basically wrote the code I was looking for. I will be posting this code
shortly as a reply to my original post in the Nested Blocks discussion.
The purpose of putting block insertions inside of a parent block is to make
it easier to insert the parent block with all the inserted blocks positioned
correctly in the parent block (relative to the parent) with one insertion
command. Also the parent block is one that is being created according to my
specifications whereas the nested blocks are client blocks that I'm not sure
will always have the same insertion points.
Ultimately I need to explode the parent block anyway, as it wouldn't meet
the client format. The solution that Jerry came up with was to locate the
nested blocks prior to exploding the parent (using the insertion points of
both the nested and parent blocks and summing these together using a
Transform method), exploding the parent, and then locating the formerly
nested block, and changing the attributes. In this way the attributes for
each instance (or reference) of the remaining block (or blocks) can all be
unique.
It was all clear to me at the time, but based on your comments here I see I
wasn't clear enough.
Edited by: HEnnulat on Nov 12, 2009 3:52 PM