Topic: Rotating attribute problem

[Keith™]

I have an issue I am trying to resolve. I have a user who has just migrated from A2k4 to A2k8. In 2004, there exists no problem, however, in 2008, using VBA to programmatically insert certain blocks with attributes causes the attributes to be rotated to 0 degrees.

If the block is inserted manually, everything is cool ... is there something different in VBA in 2008 that causes this or is there a setting somewhere that I am not aware of? .. ok that last part is loaded .. there are lots of settings that I am not aware of ..

[hendie]

hi Keith,
see http://www.theswamp.org/index.php?topic=21859.0

[Keith™]

Ah .. cool ... perhaps we should remove this thread ... or perhaps I'll just watch the other thread.

Thanks

[David Hall]

Keith, are you just inserting a block just like we always have or did you code it differently this time?  I am interseted in seeing your code if poss

[Keith™]

Same as always ...

I can't divulge the code as a whole, but I can offer this tidbit just to see what is going on ..

Code: [Select]

If Activedocument.ActiveSpace = AcModelSpace Then
    Set blk = Activedocument.ModelSpace.InsertBlock(InsPt, BlkName, Xscl, Yscl, Zscl, 0)
Else
    Set blk = Activedocument.PaperSpace.InsertBlock(InsPt, BlkName, Xscl, Yscl, Zscl, 0)
End If

MyAtts = blk.GetAttributes
For X = 0 to Ubound(MyAtts)
   strTag = MyAtts(X).TagString
   Select Case strTag
   Case "IDNO"
      MyAtts(X).TextString = "Some random text previously defined"
' lots more case statements here
   End Select
Next X

I did just notice that in certain circumstances, the block is programmatically rotated after the attributes are filled in like such ..

Code: [Select]

blk.Rotation = RotAng

but programmatically, it should not cause the attributes to be changed from the original rotation settings in the original block.

I think I'll try making sure the blocks are at 0 deg only when inserting them and see if it makes a difference.

[David Hall]

That is weird for sure.  I think I will try and recreate the problem here

[Keith™]

This issue has been resolved and I will attribute it to a bug in AutoCAD 2008. Please see this thread for the resolution.