Furthermore, it is better than command EXTRIM in Express Tools when trim along block clipping boundary because it resolved a few issues below when using EXTRIM:

• "TRIM 2:  Could not find polyline end copy point"
• "Curve must intersect cutting edges at least twice."  
• "No intersections in the interior of the curve."
• Sometimes it cannot trim properly if there is a small gap between boundary edges or in a rotated UCS plan.

• Help Button
  Bring you to this webpage

There is a function in the vlx file which can be used in a lisp or script file.

Function: (explodeall [selection])

It uses the settings saved before. If it is the first time it runs, the 'EXPLODEALL settings' dialogue is shown.

You need define [selection] first and pass it to the function. If [selection] is nil, it prompts to select objects.

The function can only be used in current layout. You need go through all layouts via lisp file and repeat the function to explode all entities in all layouts. 

The function checks system variable UNDOTRL. If it is not 0, it sets UNDO as NONE and will retrieve it to ALL when function completes.

To speed up the procedure, this function may lose some accuracy when dealing with objects in dotted linetype and need trim. These objects will be converted to continuous linetype if the entity is not able to be trimmed with TRIM command. On the other hand, use command EXPLODEALL can get the best result but it may takes a longer time.

1. All previous selected entities including exploded entities are in the "previous" selection set, so you can use option "p" to retrieve these objects under any "Select objects" prompt in following commands.  
2. It takes extra time to change the colour or layer of exploded objects to "By parent block" or "As shown on screen".
3. In a complicated drawing, you can use function (explodeall (ssget)) to select objects with UNDO being turned off. It may shorten the program running time because no need to store undo data. You may need backup the file before running it because you can not undo the operation in this scenario.

1. When parent block layer is off or frozen, and "Delete entities on turned off/frozen layers" is on, then the sub-entities on Layer 0 are changed to parent block layer.
2. When Layer 0 is off or frozen, the sub-blocks on Layer 0 are changed to parent block layer.
3. Attributes on a turned-off layer or a freezed layer are not converted.
4. All locked layers will be unlocked temporarily and the layer status recovered when process completed.
5. Sub-blocks on freezed layer will not be exploded. These blocks are deleted if "Delete entities on freezed / turned off layers" is selected.
6. If the parent block layer is off, "By parent layer" option doesn't not change its sub-entities' layer except they are on Layer 0. 
7. If a hatch/image entity inside a block is partially clipped by block clipping boundary or a wipeout entity, a new hatch/image will be created with new clipping boundary. But if the hatch pattern is gradient, it may looks different from the original.
8. If imageframe is set to 1 (show and plotted), and some of the image edges are clipped off, the new image will show all edges plotted.
9. In AutoCAD Architectural, the wall cleanup lost if a wall entity is clipped at a block/wipeout boundary.
10. Wipeout is good but sometimes a pdf file containing wipeout causes trouble. If the "print as image" option is not selected or the pdf file is not optimized properly, the wipeouts printed as black blocks.
11. If some xrefs cannot bind for unknown reason, it prompts "Binding xref unsucessful: "[xref name]" may contain unloaded nested xrefs." Sometimes an error may occur. So the best way is check and ensure all nested blocks are loaded. If you don't need nested block shown in the master drawing, "overlay" it in xref instead of "attach" it.
12. EXPLODEALL can avoid file crashes caused by command trim along a polyline bounday, but it may result in an inaccurate trim results. You need download the latest patch from Autodesk to resolve trim command problem first.
13. If customized hatch pattern definition is not found, EXPLODEALL will explode the hatch instead of apply the new boundary to it.
14. Hatches in dynamic blocks may not display properly after explosion, you have to erase it manually or turn its layer off if them have been put on separate layers.
15. It may take a few minutes, half an hour or even more to complete in a complicated drawing, especially a drawing contains wipeout or clipped block which has complicated boundary with more than 200 nodes. Please wait until AutoCAD comes back even if it becomes "No Responding".
16. Sometimes you may need REGEN to show changed object color.
17. When bind xref with "Insert" option, some objects in turned off layers of xref may appear. This is because there is a layer with the same name of the layer in xref. The layer in current drawing is "ON" but in xref is "OFF". Thus when the xref is bond with "inserted" option, the layer status follows master drawing layer status, so even the layer if "OFF" in xref, now it is "ON", and objects on this layer appear.
18. Please check the wipeout itself whenever EXPLODEALL cannot work properly with the option "Trim off entities behind wipeouts". Sometimes wipeout has nodes which are very close to each other. In this case, you need REDRAW the wipeout first, send it under the original wipeout (with DRAWORDER command), delete the old wipeout, then use EXPLODEALL.
19. At moment, it is unable to identify if block has an inverted clip boundary. So please avoid inverting x-clip boundary on blocks if you are going to use EXPLODEALL.
 

• Multiple "Explode" option
• Explode block to host layer
• Block expode Variable
• Is there a way to preserve the xclipped viewable areas and eliminate the hidden areas?