Unbundle by name returns wrong value

[M_Peeker]

Hi everyone.

I just saw a strange behaviour that I cannot reproduce, thought I'd get it into the open to see if anyone else has seen it.

To start with, LabVIEW 8.6 on Linux/Kubuntu (not supported).

A member of a LVOOP class unbundles a calibration factors that is typically 1. All of a sudden, after adding functions to this class and an attribute to the parent class, the calibration factors are returnedwrong. I get a value in the magnitude of E-315. Probing the class that goes into the unbundle shows the value being 1. Now I do control+shift+run to force a recompile (exactly what does this do?), and now the code works again.

Anyone seen this? Has it got to do with Kubuntu?

Regards

//Martin

[Davidek]

Hi Martin

I haven't seen this behavior before, but as a rule when you update a definition that you unbundle (like a cluster control, class, etc) it as always a good idea to reload it. If it's just a single unbundle that's concerned you can just re-choose the parameter you want in the unbundle list, but if there are a lot of them recompiling is more convenient.

Best regards

David

NISW

[bla457645]

I remember this problem. I didnt expolre youre vi. For some reason LabVIEW runs into issues with that (un)bundle by name. Check the clusters you use by selecting "Reorder Controls in CLuster..." The cluster might have changed during the project. In that case be sure that all your clusters comply with each other and rewire the (un)bundle function which returns the wrong value.

Yours RZM