Topic: Get Block

[Joker]

I did a search and found out what pseudo code is.  If I understand it correctly, Pseudo Code is a shopping list of tasks that the program needs to do in order to get what you want.

Here is my pseudo code:

Code: [Select]

User picks block to export
The block maintains the name
Export the block to new location
Maintain insert point
Explode the block
Collect all new entities in a list
Set to layer 0
Maintain colors the block provides
Set linetype to By Block
Insert Block to 0,0
Purge
Save
close
End of pseudo code

[T.Willey]

You are correct about the term pseudo code.  We are giving you the pseudo code so you can do some research to learn how to do it.  Take what we give you and run with it, and if you have questions, post back and someone will answer it for you.  You stated that you want to learn with this one, so this is you chance to get started, or do you need a push to help you out?

[Joker]

You are correct about the term pseudo code.  We are giving you the pseudo code so you can do some research to learn how to do it.  Take what we give you and run with it, and if you have questions, post back and someone will answer it for you.  You stated that you want to learn with this one, so this is you chance to get started, or do you need a push to help you out?

Could you please give me a push in the right direction?  Once I get pushed in the right direction and start to figure it out.  I will be back with questions and so on.

[T.Willey]

Could you please give me a push in the right direction?  Once I get pushed in the right direction and start to figure it out.  I will be back with questions and so on.

My pleasure.

First off I would select the block to exported from the screen.  Either use "ssget" with a filter list for only blocks, or use "entsel" and then make sure you have a block.  For both the filter list, and to make sure you have a block, you will need to look at the dxf code.  You can access this from the help files.  Once you select the object, you can get the entity data of the object with "entget".  From there you can get the block name (dxf code 2).  This should be enough to get you started.  Have fun.  You can also search for little tidbits of help if no one is on to help you out.

Have fun!

[nivuahc]

Code: [Select]

User picks block to export
The block maintains the name
Export the block to new location
Maintain insert point

I would start there and build on it. That's just me. Too much information tends to overwhelm. YMMV.

[Jim Yadon]

To start with, my LISP skills are limited. So please just take this as an observation.

Did you all consider that some folks may have entities already existing at or in the vicinity of 0,0? You could avoid the potential hazards of picking up extra 'passengers' when the block gets re-written.

Code: [Select]

User picks the block to export.
Pull the object from the selection set to the clip board.
Open a new drawing.
Paste to drawing.
Acquire insertion point info.
Explode.
Clean.
Purge.
Rewrite to a new file maintaining insertion point info.
Close new session.

[Jeff_M]

Rather than insert & explode, just set an Undo Begin, get the block name from a selection, get the block object from the block table, edit the block objects direct for color, linetype & layer, then Wblock out the block....bam, yer done. Then set Undo End then Undo Back.

Just my $0.02

[Jim Yadon]

Rather than insert & explode, just set an Undo Begin, get the block name from a selection, get the block object from the block table, edit the block objects direct for color, linetype & layer, then Wblock out the block....bam, yer done. Then set Undo End then Undo Back.

Just my $0.02

Out of curiousity, why would you put the UNDO code in there? I don't see why you'd need it at that point.

[Jim Yadon]

Because the Block table has been modified, and you dont want that change to persist.

That's why I am asking. It would seem to me that if you were going to the trouble of stripping a block down to the bones (aka zero layering it) to write it to file for later use, that you'd want those changes to persist in the drawing that it's already existing/being used in. Hence, ' why the UDO? '. Make sense?

[Jim Yadon]

Sorry. I got so hung up on trying to understand the undo that your notes didn't sink in.  :ugly:

[Jeff_M]

Jay,
I wouldn't use the Undo in my rendition of this for the very reasons you pointed out. But as Kerry also pointed out, that's pretty much what the OP requested.

[CAB]

Jay,
I wouldn't use the Undo in my rendition of this for the very reasons you pointed out. But as Kerry also pointed out, that's pretty much what the OP requested.

That is the way I understood the request but I'm nit sure that is the desired result. joker will need to clarify that point for us.
I personally would keep the changes in the parent drawing.

[CAB]

Rather than insert & explode, just set an Undo Begin, get the block name from a selection, get the block object from the block table, edit the block objects direct for color, linetype & layer, then Wblock out the block....bam, yer done. Then set Undo End then Undo Back.

Just my $0.02

When you say "wblock out the block" are you actually saying "wblock out the insert"? Just want to have it clear in my mind.
If you are wblocking out the insert, what if it is scaled and/or rotated?

[CAB]

I believe Jeff meant "duplicate the definition", which is the way I also read the request.

Kerry could I trouble you to clarify that?
By definition you mean the 'Block definition in the block table' and not the Insert.
By duplicate you mean create a new definition in the block table?

[CAB]

While the smoke is clearing, one more step.
If the insert is scaled and or rotated the we should not use that object to duplicate.
So to wblock you can not use a 'Block Definition', you need an Insert?
Therefore we are back to Insert & Explode?