[BUG] Vision: Selected component moves to mouse clicked coordinates sporadically

This has been a long term frustration for me and a colleague of mine since first starting to use Ignition 3 years ago. I haven’t yet checked to see if it happens in v8, but certainly all versions of 7.7+ that i’ve tried, including 7.9.12. Edit: happens in Windows 7, 10, server 2016

Sporadically, but not uncommonly, after editing a component’s properties (might include adding an event handler script, binding expression, etc.) and then clicking on another area of the Window design area to deselect the component, the component will sometimes be moved to the location I clicked. Undo will not undo the move, as I suspect it is a bug and is not captured by the undo stack.

Here is a screen capture of it happening. This took 1min 30s to happen, clicking on different components and opening various property bindings, but i’ve cropped it to keep it short and uploadable:

https:/uploads/iatesting/original/2X/3/3773702c3076c724a8eb74104de8cfc9afbddfb5.mp4

See component moves after last open of a binding editor, then finally clicking outside of Window display area. black Boxes added to hide confidential property.

Edit:
When the component moves, you can only select the component by clicking on where it moved from; clicking on the component where it moves to will deselect it, as if it hasn’t actually moved there (seems like a phantom component). Also, saving and closing the Window and reopening will show the component back in its original place… However, if I resize the component after it moves, it then accepts its new position.

Interesting. I’ve never seen anything like that, in 12 years with Ignition and IA legacy products. What OS? {I’ve always used Linux with Ignition, which might be relevant.}

You probably guessed it already, but Windows ;). Both 7 and 10 (+ server)

Yes, I think I’ve seen this on Windows too, albeit more rarely than it sounds like you have.

For me it happens every day, multiple times a day.

Still happening in 8.1.9… and yes, Windows 10…

Any kind of consistent replication would help a lot in getting this fixed. I suspect no one in IA, or at least in QA, has had this happen (often enough) to file a ticket for it.

That’s the thing: it’s not consistent and it’s hard to replicate…
Usually, when that happens to me, I try to do the same steps again, and it won’t happen.
Then after 2 hours or 8 hours or 5 minutes, bum… happens again.

And it happens exactly as @nminchin said in the first post.

For what it’s worth, I notice this far more often when I’m working in a VM rather than on the base OS. (All Windows 10 Pro or Enterprise)