Insertion point wrong for block.

[dvrVSNMW]

Hello,

I made a block and I want to insert this via toolpalletes. (file in attachement).

But the insertion point is wrong and I don't know how to fix this...

As you can see I placed a "base point" in the drawing so I thought this was the insertion point. It used to work but now due to a lot of changes in the drawing. It doesn't anymore.

Anyone can help me out this one pls?

[dvrVSNMW]

Extra info.

In attachment is an old file with a good insertion point. When I edit this drawing it also ask me to open it in block editor. The new file doesn't. So there is also something not 100% correct I think.

[h_s_walker]

Seems to work fine in LT2016

[Libbya]

If you aren't dynamically altering the base point position, then there is no reason to add a base point parameter.  

It sounds like you might be inserting the drawing that houses the block as a block, rather than just the block itself.

[dvrVSNMW]

Hello,

I just inserted the drawing via toolpalletes and the problem now is the following.

The insertion point is bottom right... weird. And the inserted block is not a dynamic block no more... how do I fix this?

However, if I open the test.dwg in attachment... this is a dynamic block I think... ?

Anyone an idea what I do wrong?

[Libbya]

How are you creating the tool for the tool palette?

[dvrVSNMW]

I have this file on my desktop and I drag it over to my toolpallete. Just as simple as that.

[Libbya]

That is why it is not working, just like I said in my last post.

If you drag the FILE onto a tool palette, then when the tool is used, it will insert the entire FILE as a block.  The dynamic block would be a nested block within the file block and the base point will be the origin of the FILE (not the nested dynamic block within that file).

Instead of dragging the FILE onto a tool palette, save the file and then drag the **BLOCK** from model space onto the tool palette.  That way the tool will insert the BLOCK instead of the entire FILE the block is nested in.

[dvrVSNMW]

Ok, good to know what I did wrong.

But I don't know what you mean with this: "Instead of dragging the FILE onto a tool palette, save the file and then drag the **BLOCK** from model space onto the tool palette. That way the tool will insert the BLOCK instead of the entire FILE the block is nested in."

I don't know how to do this... 😕

I have saved the file on my desktop. So far so good I think? But next I don't know.

Can u help me with this pls?

EDIT:

If I do it with the file in attachement it works totally fine... I drag it into the tool pallete and works perfect.

[Libbya]

I think the piece you may be missing is the difference between a file with a block inserted into it and a block file (created by saving a block as a file, using WBLOCK, etc...).  You can insert any file as a block into another file.  If the file you insert as a block into another file has a block in its model space, then that block will now be a nested block within the block that was the host file.  If instead you insert a block file (that was created by saving a block as a file, WBLOCK, etc...) then that block will insert directly into model space. 

The same distinction holds true for making tool palette tools.  If you drag a file onto a tool palette then the file will be inserted as a block.   Again, if the file you used to create the tool has a block in its model space, then that block will now be a nested block within the block that was the host file.  If, on the other hand, the file you use to create the tool palette tool is a block file, it will insert the block directly into model space.  An alternate way to create a tool that inserts a block directly is to drag a BLOCK from MODEL SPACE onto a tool palette rather than dragging a FILE onto a tool palette.   

I don't know how to explain that more simply/clearly.