CANNOT EXPLODE A BLOCK IN AUTOCAD CODE

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.

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: '

CANNOT EXPLODE A BLOCK IN AUTOCAD CODE

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(). Remember that Blocks can be scaled, clipped using the XCLIP or CLIPIT commands, etc so consider other options before exploding them.Time to go back to basics. Find Allow Exploding option in this palette. the Properties palette if you decide that you need to explode a block. If they have been created as blocks is for a reason, so exploding them might screw up someone else's effort. Also, how do I enable explode block in AutoCAD Press Ctrl+1 to open it. You can lock a block so that it can't be exploded by turning off this option. Deselect it means EXPLODEALL will remain unexplodable blocks, but EXPLODEALL still. The Block should explode.Īs I said before, be careful about exploding blocks (specially in a multiuser environment). Select this option to enable explode blocks which are not allowed explosion.

Now select the Block, enter X for EXPLODE. You will see that the 'allow exploding' option is unselected. Then on the drop down list search for the block you are unable to explode. The trick is to open the block definition dialog box (type 'b', or 'block') without selecting anything. If you don't know that this exists, you might find yourself unable to explode a block that you really, really, really need to explode (I am no fan of Block exploding, I mostly hate people who do that as a hobby, but sometimes you do need to explode them). One of this is the option to not allow the block to be exploded. When a Block is created there are several options that sometimes are overlooked. Do you find yourself unable to explode certain Blocks? Don't despair, the solution is easier than you might think.

Cannot explode a block in autocad