Redefine Dynamic Block Resets Scale Parameter

[Anonymous]

Hello community,

I am having trouble with a block which I made for a tree in plan. The tree block works well enough for what I need it to do. But whenever I modify the WBLOCK and Redefine it in a drawing, some or all of the scale parameters reset to the original size that the block was created in. Can anyone explain why this is, and if there is a way to get them to stay as they are?

I have attached the WBLOCK file of the block for reference.

Thanks,

Nick

[Libbya]

Are you sure it is the parameters/actions that are reset and not just the associative hatch?  Linear parameters and scale actions should not reset with a redefine unless you have changed their name/properties in a way that CAD cannot follow.  Associative hatches will reset and lose their associativity, though.  Your one diagonal hatch would be very easy to explode and simply scale the lines or place a nested block and scale that rather than just the hatch.  

[Libbya]

If you are seeing the parameters themselves reset, then please post a screencast of your process that causes them to reset.  

[Anonymous]

God you're good!

You are exactly right, all of the hatches are losing their associativity. It sounds like I will need to go with the exploded hatch or nested block option.

I don't think that the exploded hatch will be suitable for this (correct me if I am wrong) because the spacings of the hatch need to stay the same width. That's why I went for the associative hatch over linework.

Can you please explain/ link me to what you mean by a nested block?

Thanks again,
Nick

[Libbya]

I hadn't thought about the line spacing.  Both exploded hatch and scaling a nested block will scale the line spacing.  I don't see an easy workaround.  Bummer.

[Anonymous]

All good, thanks for lending your brain!

[Libbya · Accepted solution]

I looked at that some more and saw that the hatches did not actually lose associativity, they just reverted to their original size until you select the grip (diameter) and then deselected it.  Then they snapped back to the correct scaled boundary.  After noticing that, I figured that triggering that change might be possible on a global scale.  Yup, it is.  See the following screencast.  

[Anonymous]

Hey Libbya,

This is perfect! I love the work around you have come up with.

It wasn't quite working properly for me and was bugging out fairly often. But this was due to the complexity of the polyline used in the block. Once I re-traced the outline with less nodes, it works perfectly.

Thanks heaps