Originally Posted by
mderr904698
Sorry if i wasn't clear. I don't work through the xref. It's just the easiest and most prevalent example of the problem. I agree that locking the layer the xrefs are on would help that problem and the command reactors solution sounds interesting. It is also easy to tell that the xref has been moved by listing the properties and setting x,y, and z back to 0. But an active object (say a surface object, or even worse, a pipe object) that is live in the drawing is susceptible to the same problem.
i would prefer to use move (a deliberate action) to dropgeom (a possible unintentional action) to do something with such repercussions.