@paul_cardinale wrote:
There's a bug pertaining to the coordinates of objects inside a cluster (I don't remember the details).
The thing you're searching for might be inside a cluster constant.
I think you might be just a few degrees off Paul.
The thread bothered me.....kind of like a "Spidey Sense." I am pretty sure that I have never been bitten by a genetically engineered, radioactive VI but!...
Text search is the only way to find those silly BD object Lables that have been accidentally moved away from one of the nine snap justifications and then moved further away with a "make space". Either by a intentional make space or a bad cleanup. Call the label an orphan!
I think what is seen is the unshown text of a hidden label that is "Orphaned" from the owning object. This CAN cause an object.bounds property to become irrational. Without examining each and every object bounds there are few tests that can find an orphan lable.
The text search is one! It can look for object labels even when hidden. It does fail to identify the object it is part of though.
Basically, you have an indication of an irrational (not insane) Object. I can't say it's a bug....more of a dev error identifier.
Find the object! Show the lable! Snap it back to some justification.
Lock labels by default if desired
Lable or label? F it whichever.
EDIT: Paul will likely have a vi by end of day that scripts out a search for orphan lables, shows them and rejustifies them to the owning object after adding garish coloring and additional derogatory remarks addressing the developer's probability for Darwinian competition success.
Kudos to you!
"Should be" isn't "Is" -Jay
