We might also just let it drop out of scope Go through the results and recurse, exploding the Add our handler around the explode call, removing it ![]() Define our handler to capture the nested block references Var toExplode = new ObjectIdCollection() Here is some code snippet from the web for reference. In terms of the first limitation, the BlockReference.ExplodeToOwnerSpace only looks after the first level block definition, somewhere on web introduced a workaround, using the ObjectAppended event to capture those block references that are resulted from the explode operation and call the BlockReference.ExplodeToOwnerSpace on them recursively. There may be some other limitations but we will not corver them in this article. Another severe limitation is that the BlockReference.ExplodeToOwnerSpace method does not return the resultant entities back so as for us to take any further operations onto them if we like. Instead, they will still be kept as block references and be added into the database. ![]() That is, for nested blocks inside the root one (needless to say, those nested two or more levels away), they will not be addressed by the BlockReference.ExplodeToOwnerSpace. The first is that the BlockReference.ExplodeToOwnerSpace method only takes care of the first level of the block definition. ![]() However, it has some severe limitations as well. NET class BlockReference has a method, ExplodeToOwnerSpace(), which can explode itself and add resultant entities into its owner space, either Model or Space.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |