I have too, sadly. But that's not particularly helpful either. But never mind the messages. The error isn't triggered when the file is renamed, but it is triggered when it returns to the previous name. So why is it chaining all the way back one reference deep (or more, possibly, in an arbitrarily conceivable scenario) in order to access linework that is entirely unrelated to what I'm mousing over?
And there are another dozen questions I have about this, really.
And there are another dozen questions I have about this, really.