I have an application made in LabVIEW 8.5 that shows some peculiar behaviour from VIs that work on references to a tree control (not that I've tested it with other controls yet though):
If the reference to a tree control is passed directly to the subVI that works on it (using property and invoke nodes) things work fine both in the development environment and in built applications.
If however the tree reference is passed through a sub-VI (in other words the VI actually using it is a sub-sub-VI), things does not work in built applications. Instead you get error 1055 (invalid reference).
A cure for the problem is to tell the application builder not to remove the front panel of the sub-VI that passes the control reference (no change required for the sub-sub-VI). This is easy enough if you are aware of the problem and only have a few such VIs, but it is a nasty source of bugs/test requirements in a larger application....
Has anyone else seen this and is there something more elegant that can be done? Unfortunately I have not been able to recreate the problem in a simple demo, it seems that there must be some complexity involved for it to appear (although in this case it appears in several VIs working on different tree controls). Finding the conditions that create the problem will probably take quite abit of work...but if anyone else has seen this we could establish that it's not a unique case.
