I inserted an attributed block into a drawing with another attributed block. What i was trying to accomplish (and have done in previous versions) is use the BLOCKREPLACE command to swap out the old block for my symbol, then ATTSYNC the replaced blocks and set the attribute on them globally using SELECT SIMILAR. The problem i'm getting now is that after i ATTSYNC the block it's rejecting any input in the properties palette. The attribute inside the block does have a preset value, and after changing it in the block editor and re-attsync, it still doesn't update. Can anyone replicate this in C3D 2013 x64?
I usually just use the -insert command to replace old blocks with new ones. it will keep all attribute data associated with the block.
Yes but with a survey files with hundreds of blocks like this, that would be very time consuming.
The purpose of this is to see if anyone can replicate the problem so i can figgure out if it's just me or if a bug report needs to be filled out.
...but thanks for trying to help...
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Could you post your two blocks for testing?
The original file appears to have been made with Land Desktop. My blocks are on the E-UTIL-APP layer and the originals are located on their own independant layers. I was able to get a work around by inserting my blocks inside theirs and exploding, but like I mentioned before this is purely for testing. I'm also curious if this happens with blocks made in 2013 as well. I havn't had time to test it out yet being the buisy time of year and all.
I can confirm the behavior. The attribute of the replaced blocks cannot be edited in the properties pallet. If you make copies of the replaced block, they behave normally.
I don't have an explanation as to what causes this.
I think it may be corrupted block information created by LDD. I tested it out on some older blocks not done in LDD and it seems to work just fine. I guess we'll just chock it up to compatibility problems. Thanks for the assistance guys.
I suggest you submit the issue to support. They may not be aware of the behavior.
Can't find what you're looking for? Ask the community or share your knowledge.