From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
I do believe I've found a bug in LV6. Get the "Pages" property from a Tab Control Property Node. This returns an array of refs to each page. Then index the array at whatever to get a single page ref. Send this to a Property node and read the property "CtlsOnPage". This returns an arry of control refs found on the page. Send This array to the SizeOfArray function and display the output. Throw some controls on the tab Control, and test to see if the array CtlsOnPage size matches the number of actual controls found on that page. When this vi is executed in the LV development environment it works fine. However, when you try to incorporate it into an app using the application builder the CtlsOnPage array never gets filled.
I would be interested to hear if anyone else has experienced this problem and how they were able to fix it. ~Steve
I had the same problem with the pages property. I posted here about a week or two ago. Title was something like "bug in LV6 tab control". NI responded saying the bug is fixed in 6.0.1 but read the disclaimer first.
Jared.
"steve rino" wrote: >>I do believe I've found a bug in LV6. Get the "Pages" property from a Tab>Control Property Node. This returns an array of refs to each page. Then>index the array at whatever to get a single page ref. Send this to a Property>node and read the property "CtlsOnPage". This returns an arry of control>refs found on the page. Send This array to the SizeOfArray function and>display the output. Throw some controls on the tab Control, and test to>see if the array CtlsOnPage size matches t he number of actual controls found>on that page. When this vi is executed in the LV development environment>it works fine. However, when you try to incorporate it into an app using>the application builder the CtlsOnPage array never gets filled. >>I would be interested to hear if anyone else has experienced this problem>and how they were able to fix it. ~Steve