Trimming everything outside a closed Polyline

[neophoible]

I'm was not up to speed on my understanding of Cookie Cutter exploding the blocks. Is it an option for the blocks to be left intact?

Yeah, it sounds like there may be some speaking past each other here. One indication is this particular comment:

But you can clip them without affecting the block definition. Probably hard to do with code but can be done manually after using cookie cutter.

CookieCutter is code, a LISP routine, and this is what we were talking about, mostly. When you say it is probably hard to do so with code, you sound like you are talking about using something other than CookieCutter. The it here would be trimming a block. Bobzy20 simply misstated what CookieCutter can do. CookieCutter does not have an option to leave a Block intact. It explodes any blocks, then trims the results.

 

Here are some statements. Anyone wanting to correct or clarify, feel free. The first three are points I tried to make early on. dbroada tried to explain more clearly. I had thought he did a good job. Actually, I still think so. Anyway...

 

1. CookieCutter2 does not TRIM Block Insertions.

2. CookieCutter2 can EXPLODE a Block Insertion, then TRIM the results.

3. Block Insertions cannot be TRIMmed, though the Block Definition could be edited or a new Block Definition could be created without changing the original Block Definition.

4. CookieCutter2 does not edit or create Block Definitions.

5. WIPEOUT can be used to mask part of a Block Insertion without EXPLODEing it. This can look a lot like TRIMming.

 

I'm glad Bobzy20 found something that works for him. I'm sure that CookieCutter will work for a lot of people. It's a great routine. It just doesn't keep the Block Insertion intact. It EXPLODEs it. If you need to keep your Block Insertion intact, CookieCutter2 will not help. WIPEOUT may be a workable alternative for many situations. It does not EXPLODE the block, but neither does it TRIM it. It masks it, or part of it.

[RobDraw]

When I tried the CLIP command on a block, I wasn't sure it would work but it did. It works exactly like XCLIP. Since WIPEOUTs can be troublesome, I thought this would be a better alternative. My comment about doing it with code referred to CLIPping in a similar fashion as COOKIECUTTER but with LISP. If CLIP could be worked into COOKIECUTTER, that would be something magical.

[neophoible]

When I tried the CLIP command on a block, I wasn't sure it would work but it did. It works exactly like XCLIP. Since WIPEOUTs can be troublesome, I thought this would be a better alternative. My comment about doing it with code referred to CLIPping in a similar fashion as COOKIECUTTER but with LISP. If CLIP could be worked into COOKIECUTTER, that would be something magical.

OK, now I think I'm following you. This is a separate part, but a very important part, and one I was not aware of. I have huge gaps in my AutoCAD experience. I think earlier I admitted to large gaps. The next time something comes up, I will probably have to admit to gigantic gaps, and it may not end there! But I'm always happy to learn that AutoCAD is even better than I know.

 

You are right. The CLIP command seems to behave just like XCLIP and it works (they work) on Blocks. Since CookieCutter will EXPLODE Blocks, perhaps combining with EXTRIM would be a better route?

 

CLIP/XCLIP is a very powerful tool. In my estimation XCLIP rates as better than TRIM for Blocks. So, I'm going to have to eat my words. Semantically, you may not TRIM Blocks, but you can XCLIP them, which is even better. You can invert the part that is blocked out, you can even undo it later. I'll have to stop here and defer to those who have real experience.

 

Thanks for the tip, RobDraw. Very nice.

Edited May 22, 2013 by neophoible
added thanks

[neophoible]

Well, I don't know much about XCLIP for blocks, but here are a few notes from a bit of testing in v2012:

 

1. Works even on Dynamic Blocks.

2. Works using polygonal boundary.

3. Boundary must not self intersect.

4. Important Sysvars: XCLIPFRAME & FRAME.

5. Boundary is selectable.

6. Boundary moves with Block.

7. Boundary is editable and has grips.

8. Boundary is Delete-able via XCLIP.

9. Only one boundary allowed per block.