rgrunwell

I use case structures as part of state machines, and with large programs having many states, it becomes difficult to distinguish sections of related states. Some sort of delineation, user configurable but functionally invisible, would help organize and break up an otherwise unfathomable list. Possible implementations could be as simple as being able to insert a line between entries. Other possibilities could be the setting of the background behind the case text, the text color, or the text style.

Thanks, Jim! -Randy

Hi All- I have run into a roadblock while trying to write a general program to read/write VI controls. The finished program would use the VI control references, read the value of each control as a variant, convert it to XML, change the value in the XML, convert it back to a variant, and replace the original control's value. I was getting an error (#91, Property Node (arg 1)) that I have narrowed down to this: LabVIEW does not allow you to convert XML to a populated variant; it creates only a blank variant. The attached file shows this problem. I am not modifying the XML data, and I am using the original variant as the Unflatten prototype, but the error occurs. In effect, the reciprocal XML function does not work on variants. Is there any way around this problem? Is there a method to create a deterministic non-blank variant? I am planning to investigate importing and exporting variants to a non-LabVIEW DLL, but haven't had a chance yet. And, yes I know, I can use strict type definitions, and that will work fine until you get to clusters. I am just trying to make it universal, and avoid the complexities of unknown clusters! Thanks- -Randy Download File:post-1393-1106171617.vi