01-17-2011 02:55 PM
A little clarification on that Reported Version field in a Known Issues List...
The Reported Version field doesn't specify when we found out about a bug, but who is affected by the bug. In this case, we actually found the bug only a few months ago. A reported version of 6.0 means that all versions of CVI going back to 6.0 would be susceptible to this bug.
NickB
National Instruments
01-17-2011 05:17 PM - edited 01-17-2011 05:18 PM
Hi! Nick,
If this issue is fixed in CVI 2010, does it mean SetCtrlVal() can update the LED instantly enough without using ProcessDrawEvent()?
How about this case: http://forums.ni.com/t5/LabWindows-CVI/LED-Indicator/m-p/294514?
Many of us have known this issue since 2005.
Maybe it wasn't correctly reported as a bug...
01-18-2011 08:30 AM
Yes, in CVI 2010 and later, SetCtrlVal will update the status of the LED immediately, as it should have all along. It does look like the forum you mentioned never resulted in an actual bug report, which would explain why we were unaware of the issue until recently.
NickB
National Instruments