Clean-up drawing

[thebeesnees]

I'm looking to create a simple one-click drawing cleanup routine (macro/lisp) that includes all the actions below.

1. Select all blocks and explode (including nested blocks) - I use QSELECT for this and have to perform multiple times to explode any nested blocks.

2. Delete all wipeouts - I use QSELECT to perform this function

3. Select all items, place on Layer 0 and change all properties to BYBLOCK - I use CHPROP command

4. Delete all duplicate/overlapping objects - I use OVERKILL command

5. Fix any drawing errors - I use AUDIT command

6. Zoom extents and save drawing

I have managed to solve items 3-6 but have no idea how to convert QSELECT functions into macro format. My macro so far is:

^C^C_CHPROP;ALL;;LA;0;C;BYBLOCK;LT;BYBLOCK;LW;BYBLOCK;T;0;;-OVERKILL;ALL;;O;0.000001;I;N;P;D;N;B;Y;Y;T;Y;E;Y;A;Y;D;-PURGE;A;*;N;AUDIT;Y;ZOOM;E;

Any help would be appreciated.

[TheCADnoob]

Have you looked into the SSX command? https://help.autodesk.com/view/ACD/2015/ENU/?guid=GUID-386ADF5E-C709-4940-8DB4-909C2760A23F

[Kent1Cooper · Accepted solution]

It makes for a long macro, but some AutoLisp functions can be used in them.  This should [minimally tested in a macro] Explode all Blocks in the current space, and all nested Blocks coming from them, etc., until there are no Insert objects left to Explode:

(while (setq ss (ssget "_X" (list '(0 . "INSERT") (cons 410 (getvar 'ctab))))) (initcommandversion) (command "_.explode" ss ""))

Are XREF's a possibility?  They would also be seen by that selection, but Exploding is not applicable.

[thebeesnees]

Thanks, although not really sure how SSX command is useful in this instance?

[cadffm]

Not?

You want to create selections by objecttype or objectproperties,

ssx is the only command (commandline-only) you can do that.

But pure Lisp is better in your case, see Kents answer.

[thebeesnees]

I simply want to select all blocks, including nested blocks, and explode them - how do I achieve this using SSX?

[cadpro78]

Why do you want to explode a block?  Some blocks can be exploding but if you have multiple times that block is used in the drawing, you can't just edit to correct all of them at once. 

[thebeesnees]

The whole point of cleaning a file is to remove as much unnecessary information as possible thus block definitions, layers, etc are not required and need to be purged.

Once cleaned the file will be inserted into a master file, becoming a block, usually acting as an underlay for our own drawing work. There is no intention to manipulate these files thus block definitions no longer serve a purpose.

[Kent1Cooper]

---

@thebeesnees wrote:

The whole point of cleaning a file is to remove as much unnecessary information as possible thus block definitions ... are not required and need to be purged.

.... block definitions no longer serve a purpose.

---

They do still serve a purpose, in memory savings.  One of the primary reasons for Blocks is that the information about all the pieces inside them is stored only once, in the Block definition, and Insertions of them need only insertion point, scale factors, rotation and Layer, but don't need to hold information about all the details of all the pieces within them at ever insertion.  When you Explode the Blocks, all those separate pieces that were in all those Block insertions now have all their information [Layers, locations of endpoints and centers and vertices and so on, radii, text content, etc., etc.] all stored in the drawing file separately and independently and unnecessarily repeatedly.  If Blocks are complex and/or there are a lot of them, that will significantly bloat the file size.

[thebeesnees]

I agree in principle however in this instance I am trying keep our own drawing file as clean as possible.

We don't want all the layers, objects, block definitions from an imported drawing cluttering our files hence "cleaning" them first. The cleaned file is inserted is a block and just acts as a discrete underlay, usually placed on a grey layer.

[thebeesnees]

I've added your routine to the beginning of my macro which now looks like this...

^C^C(while (setq ss (ssget "_X" (list '(0 . "INSERT") (cons 410 (getvar 'ctab))))) (initcommandversion) (command "_.explode" ss ""));^C^C(if (setq ss (ssget "_X" '((0 . "WIPEOUT")(410 . "Model"))))
(command "_.erase" ss "")
);^C^C_CHPROP;ALL;;LA;0;C;BYBLOCK;LT;BYBLOCK;LW;BYBLOCK;T;0;;-OVERKILL;ALL;;O;0.000001;I;N;P;D;N;B;Y;Y;T;Y;E;Y;A;Y;D;-PURGE;A;*;N;AUDIT;Y;ZOOM;E;

I'm sure there are more elegant ways of achieving same results but works well enough. Thanks for help

[Kent1Cooper]

---

@thebeesnees wrote:

... I am trying keep our own drawing file as clean as possible. We don't want all the layers, objects, block definitions from an imported drawing cluttering our files hence "cleaning" them first. ..

---

There are plenty of routines around that will [for example] force everything in all Block definitions to Layer 0 and color ByLayer and so on, so you can get Layering "cleaned" without the memory waste of Exploding all Blocks.  In my opinion, a drawing is "cleaner" if exactly repeated content is contained in Block insertions instead of existing separately in all locations.

[thebeesnees]

Firstly, thanks for the feedback. Much appreciated.

The only contention I have, which may be based on my misunderstanding what affects drawing performance most, is that often blocks contained within drawings provided can be extremely inefficient. They are usually flattened exports from non-Autodesk 3D modelling software. This usually means large amounts of duplicated/overlapping objects which clearly impairs performance (anecdotally this appears to be the case).

Simply cleaning/optimising the drawing improves performance significantly and allows us to control the appearance better. Already getting positive feedback after implementing procedure in the office.

Again, thanks for the help.