Parameter passing to popup

[scott2]

Hi,
When passing a UDT to a popup via the default method or scripting, there appears to be a slight delay when the popup is opened before the binding completes.
ie. If I have motor1, motor2 that are passed to popMotor that has a display of:
Root Container.Analog::Meta.TagName
if motor1 has been opened the motor2, the text display will show motor1 for a short period for showing motor2.
Is this normal.?

thanks

[scott2]

resolved.
I referred to this thread & changed the binding from UDT to expression based & seems to function the same without the delay

Template using UDT param: Can you access UDT tag metadata?

We’ve just been bitten by this too. A touchscreen we use has a quite slow CPU, opening a motor popup took 1s to show the popup window, and another 7-8 seconds to visualise the tag data. During that time, the CPU was constantly running at 100%. I would have thought that opening a popup would be influenced mostly by network speed (getting the data from the server) or graphical power (rendering the screen itself), but it turns out to be CPU intensive. Changing the popup to accept a tagpath parame…

[nminchin]

There are numerous other reasons to never use UDT type Vision Window parameters as well. Lots of topics on this to look through if you have the curiosity

[scott2]

What are the other reasons?
I sort of understand as to why the delay is there, as the window is opened before the binding is completed.
I am assuming the reason is that all attributes are 'loaded' & therefore increase % on load.?
Is this the same reason not to use a UDT on a drop target..?