Slow property node subvi

[Ben]

---

@Ben wrote:

Locals have a special backdorr method of getting at the value in a control that bypasses the UI thread.

That is why it ran fast in the top-level VI.

When using a property node, the code will stall when it gets to the property node read while it waits for the OS to do the thread swap to the UI thread to read the value and then it will drop out of the UI thread and finish that cycle of your loop.

I would go for a LV2 Global to as the easiest fix since it will NOT use the UI thread.

Ben

---

Sorry I missed a "Not".

Ben

[JimboH]

Ben,

  Thanks for the info. I apparently took too long to write that last post and didn't see yours.

Jim

[JimboH]

Speaking of edits that might be much better if placed at the site of the foul and not at the end, although I haven't seen any explicit documentation on the matter, udp read in Labview definitely reads multiple packets at once NOT one packet per read. It is amazing all the bugs you can find once you build error checking into the system.