A coworker came to me last week with a strange Revit Architecture question. He was trying to adjust the crop boundaries on an elevation, but every time he selected the top grip, the bottom boundary moved. Grabbing the bottom grip? Yes, that one moved the top. We spent the better part of lunch trying to resolve the issue. Baffled, we finally deleted that elevation and recreated it, which got the crop boundaries behaving normally again.
But why was it doing this in the first place? As it turns out, the problem was a result of having used the Tools>Project Position/Orientation>Mirror Project command in Revit 2009. Revit mirrors the entire project, including it’s own internal understanding of the top and bottom of your elevation’s crop regions.
Solution? Delete and recreate the elevation as we did, or grab the elevation tag in a plan view, and mirror (without copy) about (your-best-guess-for-the-) center point of the elevation, and readjust the crop regions after the fact. Or retrain yourself to grab the bottom grip to adjust the top.
Note: we’ve also discovered issues with the Rotate Proect/True North tools, where workplanes don’t rotate with the view. This results in the inability to add any annotation to that view because the workplane is at an extreme angle to the view direction. I haven’t had a chance to investigate this one, though.