Moving Dimensions

[Anonymous]

I am working on a set of Construction Documents. I dimension to the center of the opening (windows, doors, etc.). I recently noticed that somehow every single dimension now has moved to one side of the opening, and is not aligned with where I had originally placed it. Needless to say, I don't want to have to go thru and re-dimension all the openings time and time again, so if anyone has any suggestions on how to keep the dimensions where they are supposed to be, that would be great. I am on AC10, with the latest library and build. Thanks in advance for any suggestions.
Here is a picture of what I am talking about, with the dimensions moved to the side.

I forgot to mention that the windows and doors are placed according to their center (not inserted either to the right or left), and the dimension is linked to the center point of the window/door.

[Anonymous]

I have never seen this behavior so I do not know how to
stop it from happening. I notice that the dimension leader
lines align with the outside of trim and prompts me to ask
if you have "show all hotspots" ON in the parameters for
the windows because if this parameter is set to ON there will
be hotspots at the outside edges of the trim.
Peter Devlin

[Anonymous]

Which I thought was odd as well, because there are no hotspots on the trim because I do not have "All Hotspots = On". Which could make sense if I did, but they are not...

[Anonymous]

Alright. So I was working on the documents further, and noticed that the dimension markers seemed to correct themselves (snapping back to the center of the opening). However, they have reverted back to correlating with the outside of opening, as illustrated with the image I attached above. This is driving me crazy. I have tried refreshing the working view, refreshing layout book, but nothing is working. They seem to flip back and forth for no reason. Any ideas as to why this is happening, or how it can be prevented in the future would be of the greatest help. Thanks in advance.

[Anonymous]

We had a similar issue with a fairly complex vanity object and it turned out to be a hotspot2 unID (unique identifier) issue within the 2D script of the object.
If that is any help to you.