2 of 2 people found this helpful
It was removed when the newest symbol editor was released. DxDesigner manages it on its own now. I haven't seen any issues with anything other than border symbols (and then only in the very first release) but that is gone now with the introduction of the symbol type Border.
So, what does it use for the extents? The pins and graphics? I hope properties are not included, because we often would have property names outside of the existing outline. I would be nice to be able to display it, even though the system is supposed to be handling it. Has there been any talk about adding that as another checkbox under Display Control?
Looks like it includes the visible properties. But it does behave differently than the bounding box. I haven't seen any overlapping symbol issues and haven't heard of any changes to expected net drawing results.
I did see a pretty crazy Variant unplaced X-out but we found properties that were the same color as the background placed far from the symbol body.
So, up til now, recognition of a border symbol has been dependent upon a tiny symbol outline and a symbol type of Annotate. Now, with a new symbol type of Border, do users have to make any changes to existing symbols that used to be recognized as borders? Also, in Automation, will Application.Query and ActiveView.Query be able to find borders with a new appropriate object type mask? And will the infamous, undocumented Block.IsBorderSymbol property, as well as the established Border select filter, work correctly with both existing and new symbols?