#Acadblockreference explode vb.net code

Let me see if I understand you correctly: your ultimate goal is to purge certain layer.

If TypeOf varEx(i) Is AcadBlockReference Then If TypeOf oEnt Is AcadBlockReference Then I'm almost there! Any help is greatly appreciated, new with VBA.

I need a statement before my IF condition to check the drawing for block references first and if there aren't any it would go to the next sub.

#Acadblockreference explode vb.net code

The code below is what I found on these forums and it works but it won't execute the next subroutine because the For statement keeps looping. I wrote some code that deletes the first block it finds, I couldn't get it to loop through and explode all of them. I have a drawing my company uses as a base drawing but there's a bunch of layers we don't want on it and the only way to delete the layers is to first explode all the blocks in the drawing. The results of calling the EXP command should be obvious enough – and do not result in anything very visually stimulating – so I’ll finish the post here.I've spent the last two days searching forums and reading through my vba book on exploding block references. Add each one of them to the current space Now open the current space in order to Explode the object into our collection Collect our exploded objects in a single collectionĭBObjectCollection objs = new DBObjectCollection () įoreach ( SelectedObject so in psr.Value) New PromptKeywordOptions ( ' Erase original objects?' ) ĮraseOrig = (pkr.StringResult = 'Yes' ) ĭb.TransactionManager.StartTransaction() Check whether to erase the original(s) PromptSelectionResult psr = ed.GetSelection(pso) Pso.RejectObjectsFromNonCurrentSpace = true Pso.MessageForAdding = ' Select objects to explode: ' There’s a lot this code doesn’t do – such as check for entities that did not actually generate any exploded results (and so probably shouldn’t be erased) or output some feedback on what is happening to the command-line – but the principle should be clear enough. Here’s a simple approach to mimicking the behaviour of the EXPLODE command programmatically: after calling Entity.Explode() on each selected entity, we optionally erase the original entities and add the results of the Explode() to the drawing. So there is some occasional – and understandable – confusion around Explode() or Purge() not working as expected. Purge() checks a list of objects for ones that can safely be erased, and then it’s up to the caller of the function to do so.

Explode() populates a DBObjectCollection with the results of the explode operation, and it’s then up to the caller of the function to add them to the appropriate location (typically the current – i.e. The way in which Explode() and Purge() differ from their “equivalent” commands is that they’re non-destructive: they don’t actually result in a change to the AutoCAD drawing database. I realised recently – on receiving this comment – that I hadn’t specifically covered the nature of Entity.Explode() in a post (even if it’s been used in a few of them, over the years).Įntity.Explode() is one of those tricky methods: it’s actually a faux-ami with the AutoCAD command of the same name, in a very similar way to Database.Purge().