Topic: Non-Explodeable blocks in 2006

[whdjr]

Using the 'block' command in AutoCad 2006 it gives you the option to make your block "non-explodeable".  Does anyone know how to change a block that is set this way or know how to explode the block?

[Keith™]

dunno ... insert as *blockname ?

[Bob Wahr]

Code: [Select]

Sub BoomIt()
Dim objblk As AcadBlock
Dim objblks As AcadBlocks
Set objblks = ThisDrawing.Blocks
For Each objblk In objblks
  objblk.Explodable = True
Next objblk
End Sub


[Keith™]

There ya go ...

[glee]

How about just redefining the block and checking the allow to explode option?
You probably have good reasons not to do so.
So I'll mosey on along..

[Keith™]

How about just redefining the block and checking the allow to explode option?
You probably have good reasons not to do so.
So I'll mosey on along..

That sounds like a good reason to disable the check box ....  :whistle:

[Bob Wahr]

How about just redefining the block and checking the allow to explode option?
You probably have good reasons not to do so.
So I'll mosey on along..

That's pretty much the same thing that I said glee.  If you want to explode a non-explodable block, you have to change it's definition so that it is explodable.

[whdjr]

dunno ... insert as *blockname ?

Sorry, doesn't work Keith.

Code: [Select]

Sub BoomIt()
Dim objblk As AcadBlock
Dim objblks As AcadBlocks
Set objblks = ThisDrawing.Blocks
For Each objblk In objblks
 objblk.Explodable = True
Next objblk
End Sub


Using your example Bob I penned this in lisp:

Code: [Select]

((lambda (/ lst)
   (vlax-map-collection
     (vla-get-blocks
       (vla-get-activedocument (vlax-get-acad-object))
     )
     '(lambda (x)
(and
  (vlax-property-available-p x 'explodable)
  (eq (vlax-get-property x 'explodable) :vlax-false)
  (not (vlax-put-property x 'explodable :vlax-true))
)
      )
   )
 )
)

How about just redefining the block and checking the allow to explode option?
You probably have good reasons not to do so.
So I'll mosey on along..

I am talking about the block command not the wblock command.

[Bob Wahr]

I don't know whdjr (is it pronounced whidjer or wahidjer?) there's a whole bunch of curvy things in that code.  Not sure how mine helped produce that mess

Glad you got it solved.  You did get it solved, right?

[MP]

OT: forgive me.

I found long ago that testing for the availability of a property via vlax-property-available-p, testing its current state, and then changing the state was far slower than just putting the hammer down inside a error trap. Not recommended as a blanket technique, but for some things it dramatically drops prosessing times where applicable and beneficial (like processing tens of thousands of drawings via objectdbx). Use carefully, again, not a blanket solution.

e.g.

Code: [Select]

(   (lambda ( )
        (vlax-map-collection
            (vla-get-blocks
                (vla-get-activedocument
                    (vlax-get-acad-object)
                )
            )
           '(lambda (object)   
                (vl-catch-all-apply
                   '(lambda ( )
                        (vlax-put-property
                            object
                            'explodable
                            :vlax-false
                        )
                    )
                )
            )
        )
    )
)
Coded blind.

PS: What was the local variable lst for Will, residual from an earlier version?

[pmvliet]

Just out of curiosity, can any other this be used when you come across a block that cannot be exploded?  Not talking 2k6, but lower versions. There have been times when you have a block that is not exploded because of different x,y scales and other things of that nature.

I can't find any examples right now, but it did spark my brain...

Thanks,
Pieter

[Bob Wahr]

No, that's a different issue.

[ronjonp]

If you open that block in an release of ACAD earlier than 2006 you can explode. Not elegant.....but it works.

Ron

[MP]

is it pronounced whidjer or wahidjer?

Ummm yes, I'd like to buy a vowel please.

[whdjr]

<...SNIP...>

PS: What was the local variable lst for Will, residual from an earlier version?

Originally after I changed the value to 'true' I saved it to a var so I could explode it before exiting the routine, but I decided against that and I guess I left the var by mistake.  Sorry, I will fix.

[whdjr]

is it pronounced whidjer or wahidjer?

Ummm yes, I'd like to buy a vowel please.

It is not pronounced any way. 

William Harold DeLoach Jr

[whdjr]

...
I found long ago that testing for the availability of a property via vlax-property-available-p, testing its current state, and then changing the state was far slower than just putting the hammer down inside a error trap. Not recommended as a blanket technique, but for some things it dramatically drops prosessing times where applicable and beneficial (like processing tens of thousands of drawings via objectdbx). Use carefully, again, not a blanket solution.
...

So...Do you always advocate speed over safety?

[Bob Wahr]

I don't do letters.  I'm going to pronounce it as something.  If you won't give your preferance, I get to choose.  As of now, you are Whidjer.

[MP]

So...Do you always advocate speed over safety?

I believe I addressed that already.

[whdjr]

I don't do letters.  I'm going to pronounce it as something.  If you won't give your preferance, I get to choose.  As of now, you are Whidjer.

Ok then Whidjer it is.   

[whdjr]

So...Do you always advocate speed over safety?

I believe I addressed that already.

[MikePerry]

Just out of curiosity, can any other this be used when you come across a block that cannot be exploded?  Not talking 2k6, but lower versions. There have been times when you have a block that is not exploded because of different x,y scales and other things of that nature.

Hi

Maybe take a look at system variable EXPLMODE.

Have a good one, Mike

[DanB]

Open the new block editor feature for the block in question and check the properties window>>Block>>Allow Exploding>>Yes/No

[whdjr]

Good find Dan.