LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Should All Property Nodes go through UI thread?

Just wondering if there is an update on the CAR (or if it's been switched to another number)...

 

*Thanks*


Certified LabVIEW Architect
TestScript: Free Python/LabVIEW Connector

One global to rule them all,
One double-click to find them,
One interface to bring them all
and in the panel bind them.
0 Kudos
Message 21 of 27
(1,998 Views)
Good question.  BTW, I notified a moderator about the accepted solution on page 2 already.
LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
Message 22 of 27
(1,989 Views)

The CAR number and priority are still the same as they were in David's last post. The best I can offer is that R&D is still working on correcting the issue, and it WILL be included in an upcoming release.

Caleb Harris

National Instruments | http://www.ni.com/support
0 Kudos
Message 23 of 27
(1,957 Views)

To review:


Larry Stanos wrote:
every property changed in a single property node triggers a control update on the screen

David_B wrote:
Alright, so I've verified the behavior in 8.5.1 and 8.6 as well.  The property node processes them all at once in versions 8.0.1 and 8.2.1.

Ben wrote:
If what you have reported is true, I , we,  EVERYONE would like to see that fixed ASAP.

 

David_B wrote:

I've just checked into the status of this CAR.  It's been given an increased priority and it appears to be a hopeful addition to the next maintenance release.  Of course, there is not guarantee that it will make it in by then, but from the notes on the CAR, it is apparent that R&D is actively working on it.



The reason for the question is that, as of September 2008, the "next maintenance release" would have been LabVIEW 8.6.1.  Since I didn't see the CAR listed for 8.6.1, 2009, or 2009 SP1, I want to make sure NI hasn't forgotten over the last 18 months.

 


Certified LabVIEW Architect
TestScript: Free Python/LabVIEW Connector

One global to rule them all,
One double-click to find them,
One interface to bring them all
and in the panel bind them.
0 Kudos
Message 24 of 27
(1,950 Views)

I ran Larry's VI in LabVIEW 2010 and the problem persists.  Can we get the CAR status?


Certified LabVIEW Architect
TestScript: Free Python/LabVIEW Connector

One global to rule them all,
One double-click to find them,
One interface to bring them all
and in the panel bind them.
0 Kudos
Message 25 of 27
(1,817 Views)

So, all I can say (unfortunately) is that it is still being worked on by R&D toward resolution in a future release. Until an issue is actually fixed, its target version isn't fixed, so I can't say for sure which version it will be. I can, however, confirm that it is still being actively worked on.

Caleb Harris

National Instruments | http://www.ni.com/support
0 Kudos
Message 26 of 27
(1,776 Views)

FYI, the referenced Property Node CAR 125593 was fixed in LV 2011. Rejoice in stability releases!

Also, I believe that the LV Help specifies for each property if it "Loads the front panel into memory", which you can use to help infer whether the Property Node uses the UI thread. And no, they do not all use the UI thread.

Message 27 of 27
(1,498 Views)