Topic: Prevent Block Explode

[T.Willey]

Add the line ' (vl-load-com) ' as the first line under the defun.  That will load the ActiveX Arx, so that lisp can interact with ActiveX ( no matter how many times you call it, the arx will only be loaded once ).  Sorry about that.

[ronjonp]

Add (vl-load-com).

** Too slow

[vegbruiser]

Add the line ' (vl-load-com) ' as the first line under the defun.  That will load the ActiveX Arx, so that lisp can interact with ActiveX ( no matter how many times you call it, the arx will only be loaded once ).  Sorry about that.

Thanks Tim, that does the trick.

[Jeff H]

that works for the blocks IN the drawing, but what about the drawing itself?  meaning, the file that gets inserted as a block needs the property set

I tried it on drawing inserted and it worked.

[T.Willey]

that works for the blocks IN the drawing, but what about the drawing itself?  meaning, the file that gets inserted as a block needs the property set

I tried it on drawing inserted and it worked.

What he is talking about, is setting a drawing explode'ability, so that when it is inserted, the block that represents the drawing is/isn't explodable.  To do that, you have to change the explodable property of the model space's block table record of the drawing in question.

[Jeff H]

what about setting the currentDrawing to explodable?  I have hundreds of blocks I just inherited that need that property changed

I think I understand you will have to do like the previous code if file is already inserted in a drawing

Code: [Select]

    [CommandMethod("ChangeCurrentDrawingExplodableProperty")]
        public void ChangeCurrentDrawingExplodableProperty()
        {
            Document doc = Application.DocumentManager.MdiActiveDocument;
            Database db = doc.Database;
           
            using (Transaction trx = db.TransactionManager.StartTransaction())
            {
                BlockTableRecord msBtr = SymbolUtilityServices.GetBlockModelSpaceId(db).GetObject(OpenMode.ForWrite) as BlockTableRecord;
                msBtr.Explodable = !msBtr.Explodable;
                trx.Commit();
               

            }

            doc.SendStringToExecute("QSAVE ", true, false, false);
        }



[David Hall]

This is what i ended up doing

Code: [Select]

[CommandMethod("CEP")]
        public static void ChangeExplodableProperty()
        {
            Document doc = Application.DocumentManager.MdiActiveDocument;
            Database db = doc.Database;
            Editor ed = doc.Editor;

            using (Transaction trx = db.TransactionManager.StartTransaction())
            {

                BlockTable bt = db.BlockTableId.GetObject(OpenMode.ForRead) as BlockTable;
                foreach (ObjectId objId in bt)
                {
                    BlockTableRecord btr = (BlockTableRecord)objId.GetObject(OpenMode.ForRead);

                    if (btr.Name == "*Model_Space")
                    {
                        ed.WriteMessage("\n" + btr.Name + " Explodable property is set to " + btr.Explodable.ToString());
                        btr.UpgradeOpen();
                        btr.Explodable = !btr.Explodable;
                        ed.WriteMessage("\n" + btr.Name + " Explodable property has changed to " + btr.Explodable.ToString());
                    }
                }


                trx.Commit();
            }
        }
I left the extra messages in the code from above so I could see it from the command line.  I wrote a script that processed the files.  It took about 5 minutes to process the files.

[danglar]

Nice routines to allow or prevent block exploding:

https://lispbox.wordpress.com/2014/12/21/alow-exploding-in-a-block-defunition-via-lisp-function/

https://lispbox.wordpress.com/2014/12/21/disallow-exploding-block-via-lisp-function/