2019-11-01, 21:22
It could be avoided but I'm not sure if this will end up in a speed penalty. It's a loop and requests the window properties 100 times. Each request for them costs a few ms of time that's why I break the loop once label1 is empty.
Because the window properties get stored in the window you are setting them.
Why don't you just hide the other dialog if the select dialog gets visible via <visible>!Window.IsVisible(selectdialog)</visible>
You can also try to set a <onclick>Dialog.Close(all,true)</onclick> before. That works better with window animations for those scenarios.
Edit:
I also can offer you a argument to force the home window as property storage. But that requires a ",home" at each property setting. That could bypass your issue.
Because the window properties get stored in the window you are setting them.
Why don't you just hide the other dialog if the select dialog gets visible via <visible>!Window.IsVisible(selectdialog)</visible>
You can also try to set a <onclick>Dialog.Close(all,true)</onclick> before. That works better with window animations for those scenarios.
Edit:
I also can offer you a argument to force the home window as property storage. But that requires a ",home" at each property setting. That could bypass your issue.
