Text displayed on top of other elements while priorities are equal and file order would mean text is drawn first.
This 'works as designed'For XM:
Elements that are at the same 2D priority or at the same 3D depth are coincident, and based on the way z-buffer [video card] hardware works, there is no guarantee which of the coincident elements is "on top".
For 2D views, we attempt to maintain file order among coincident elements when possible, but it is not possible when there is a mix of opaque and transparent elements (small text drawn with anti-aliasing on has transparency around the edges). The only way to be assured of a particular element order is to move coincident elements to different priorities or depths.For V8i:
We've changed the behavior such that anti-aliased text is always drawn after coincident opaque geometry. That means that for 2D views, the text will appear on top of an opaque shape at the same display priority when file order is requested and anti-aliasing is enabled.
For 3D files, z-buffer hardware rules preclude any guarantee as to which element appears "on top" in general. When file order is requested for a 3D top ortho view and only 2D elements are drawn, then anti-aliased text will generally appear on top of the coincident opaque shape, and if anti-aliasing is disabled, then coincident geometry will generally appear in file order.