Ok, I know you’re going to hate to hear this: but this is a feature, not a bug! Let me explain:
The Vision module’s window system is made in such a way that root container properties are special. These properties are used as the parameters for that window.
You can create a generic window, for the sake of example, let’s say it’s a pump control window. You would then put the pump ID as a root container property for that window. All around your project, you’d then open up that window, passing it a different pump ID each time you opened it. In this way, the generic window can be re-used by altering the root container properties (the parameters).
When you do a hot-update, it is actually downloading the changes to the project, closing all of the open windows, and then re-opening them in the same locations that they were at. As you’ve discovered, it also remembers the values of any root container properties, and re-sets those on the new instances of the window.
It should be obvious given the example above why this is important. If you had your pump control window open for pump “82”, did a hot-update and we didn’t preserve the values of the root container properties, your pump control window would open up in whatever state it had been left it most recently in the designer.
Not that you understand how this works, you should be able to work around it quite easily. If something is not meant to be a window parameter - don’t store in on a root container property. All other properties will get their values from the designer (or any applicable bindings)
Hope this makes sense,