Community
yes... The hard way. You have to open the BlockTableRecord of the Block in question, then BTR.GetBlockReferenceIds, and open each of the references, and almost recreate the code for adding the AttributeReference to the BlockReference when inserted, except that for existing attributes that have been modified, you don't create them as new ones, you just call SetAttributeFromBlock. Also, for existing attributes that have been modified, like you moved them, or changed the font, or visibility, etc... If the attribute has a textstring in it that is not the default, you will have to store that textstring, call SetAttributeFromBlock, then reset the textstring.
I'm a little reluctant to post my version, but here it is... attached. It takes the BlockTableRecord's ObjectID, and a regular expression for what attribute tags to Sync. The regular expression is optional and is defaulted to Sync all Tags found. To sync a single att, just pass the Tagstring. If you use it, you'll find there is a reference to the DocumentManager at the top that you will have to declare or change.
Edited by: chiefbraincloud on May 13, 2009 1:11 PM
Changed the attachments extension so it doesn't try to 'Run' when you click it.
I'm a little reluctant to post my version, but here it is... attached. It takes the BlockTableRecord's ObjectID, and a regular expression for what attribute tags to Sync. The regular expression is optional and is defaulted to Sync all Tags found. To sync a single att, just pass the Tagstring. If you use it, you'll find there is a reference to the DocumentManager at the top that you will have to declare or change.
Edited by: chiefbraincloud on May 13, 2009 1:11 PM
Changed the attachments extension so it doesn't try to 'Run' when you click it.
Dave O. 
I just noticed that you are the same poster from the other day with the Attribute not showing up (solved) but your last comment indicates you are working with a database on the side instead of the current drawing. The code I posted works with the current document, but I'm not at all sure what the result would be if you tried the same approach on a side database. At first thought it seems like it should work just by changing the DB reference to the side database but I never tried to do that level of manipulation on a side database before.
Dave O.
Did it suffer some sort of access failure, or just not overcome the justification problem?
Dave O.
Based on the apparent purpose of this function (to update title block attributes), I can see a use for it in our house as well. So, I would be happy to take a look and see if I can help find a solution. I won't really be able to get into it until tomorrow, though.
Dave O.
I've always had some sort of Lisp routine for updating title block atts, but I've never taken the time to do a .Net version, much less a .net version that works on the side instead of opening each drawing.
setting the database to the working database and then calling the adjustalignment on the attribute should do what you wanted.
There are a couple of things missing (besides TitleBlockAttributes) so I can't build it without fixing it, but it makes sense, I think that may be the bit we were reaching for. I'm personally curious now, I wonder if setting the side DB to the working database will eliminate the problem with the alignment and then calling AdjustAlignment would be unneccessary?
And, I also frequently extoll the virtues of Through the Interface. Kean's posts have saved me from many hours of frustration (and once or twice, saved me from ending it all After many hours of frustration;-)
Dave O.
Yes...That's why it is Italicized and separated... I was referring to it in the comment that followed. That in no way qualifies as PLAGIARISM.
And, If your post was intended to disrupt a perfectly civil discussion about .NET programming then it definitely IS having the intended effect.
And, If your post was intended to disrupt a perfectly civil discussion about .NET programming then it definitely IS having the intended effect.
Dave O.
