02-28-2012 11:25 AM
Hi I've recently started updating our code from 8.6 to 2011.
I have two problems which could be linked and Im pretty sure its a LabView program and not something that I am doing.
1) Type Definition References in old EventStructures are different to the currents references for a control:
Changing "Controls 1" works fine because it is not a type def. Changing "Controls 2" means the references do not match and you will get an error.
2) If a Cluster is a Type def then using the function "CtrlRefNodes[]" does not return any Control References.
Here are the Vi's that you will need to replicate the errors:
02-28-2012 11:39 AM
The first one you illustrated is a confirmed bug.
The second is scripting related... Who knows if we can report bugs with that.
Ben
02-28-2012 12:00 PM
02-28-2012 12:49 PM
I'm sorry but I'm dense, where is the bug? The code seems to be running exactly as it should. When I change Cluster 1 or Cluster two I get no error turning the CtlRef value into a cluster reference - but I do see error trying to convert it into a ring reference - which is correct. The converse is true if I change one of the ring controls - again correct.
Mike...
02-28-2012 01:10 PM
No maybe I'm being dense (or maybe just lazy) but the words describing the first bug is based on the Search function finding a match. In 2011 the control refs from the Event Property node no longer give you an "equal" when comparing them in LV 2011.
Its like the bug where you mentioned you always match labels.
Ben
02-28-2012 01:15 PM
02-29-2012 05:28 AM
I cannot go through all our code that uses EventStructures and replace them. 50+ Event strutures with approx 50 cases in each.
The amount of bugs that will creep in/ testing needed would cost us hours.
02-29-2012 07:17 AM
@LVJoe wrote:
I cannot go through all our code that uses EventStructures and replace them. 50+ Event strutures with approx 50 cases in each.
The amount of bugs that will creep in/ testing needed would cost us hours.
Ouch!
Well I supose it is obvious but you should hold off on upgrading.
In addition I usggest you contact your local NI rep and let them know about this issue. Tell them it is an "Upgrade Issue". Get them to start pulling string for you. Your local rep has the abitlity to influence (not control!) the severity assigned to a bug. High priority bugs will get fixed (if fixable) in the next release. In fact there is a possiblity this bug has already been fixed since there is a Beta version in testing now (Practically speaking there is always an Alpha or a Beta version being tested all of the time although there may not be a public version).
So talk to your local rep and ask them to look into this.
If you hear anything, plese let us know!
Your brother in (a rat's nest of ) wires,
Ben